Trace/breakpoint trap error

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Trace/breakpoint trap error

Phil B
 
I was rebuilding my image which seemed to be taking longer than usual when the VM unceremoniously exited with the following:

Trace/breakpoint trap

When I tried to reproduce in gdb, it wouldn't.  So what is this error indicating?  This was with 5.0-202002190233.
Reply | Threaded
Open this post in threaded view
|

Re: Trace/breakpoint trap error

Eliot Miranda-2
 
Hi Phil,


> On Mar 22, 2020, at 12:00 PM, Phil B <[hidden email]> wrote:
>
> 
> I was rebuilding my image which seemed to be taking longer than usual when the VM unceremoniously exited with the following:
>
> Trace/breakpoint trap
>
> When I tried to reproduce in gdb, it wouldn't.  So what is this error indicating?  This was with 5.0-202002190233.

This is ARM 32-bit right?  If so, then likely a code generator error in the JIT.  I’d like to see the crash.dmp.
Reply | Threaded
Open this post in threaded view
|

Re: Trace/breakpoint trap error

Phil B
 
Eliot,

On Sun, Mar 22, 2020 at 5:28 PM Eliot Miranda <[hidden email]> wrote:
 
Hi Phil,


> On Mar 22, 2020, at 12:00 PM, Phil B <[hidden email]> wrote:
>
> 
> I was rebuilding my image which seemed to be taking longer than usual when the VM unceremoniously exited with the following:
>
> Trace/breakpoint trap
>
> When I tried to reproduce in gdb, it wouldn't.  So what is this error indicating?  This was with 5.0-202002190233.

This is ARM 32-bit right?  If so, then likely a code generator error in the JIT.  I’d like to see the crash.dmp.

This was the 64-bit Linux VM and no crash.dmp was produced.  I've rebuilt my image half a dozen times since seeing this error and so far it is not reproducible.

Thanks,
Phil