[Mono-list] Mono process dies with "trace trap"

[Maurício Linhares]

Isn't this the sign of a crash:

Program received signal SIGBUS, Bus error.
[Switching to process 72092 thread 0x4f03]
0x03f83f1e in ?? ()


?

Checking this address, it's managed code in my app.  

-
Maurício Linhares
http://techbot.me/ - http://twitter.com/#!/mauriciojr



On Thursday, July 12, 2012 at 10:25 AM, Rodrigo Kumpera wrote:

>  
>  
> On Thu, Jul 12, 2012 at 10:22 AM, Maurício Linhares <mauricio.linhares at gmail.com (mailto:mauricio.linhares at gmail.com)> wrote:
> > Ok, I have never done any debugging using GDB, so I'm pretty lost here.
> >  
> > The page tells me to use a function called "print_method_from_ip", when I do it in a gdb session:
> >  
> > (gdb) p print_method_from_ip(0x03f83f1e)
> > No symbol "print_method_from_ip" in current context.
>  
>  
>  
> Try mono_pmip.
>  
> >  
> >  
> > How do I load these mono functions to my GDB session?
>  
> No need to load, they part of the mono image.
>  
> >  
> > The app is being loaded as:
> >  
> > gdb --args mono Sync.Mac.Cli.exe
> >  
> > Then I hit "run" and then I wait until the program crashes.
>  
> Crashes how? All you've shown was a backtrace. The complete execution,
> between run and the crash would be useful then.