[EMAIL PROTECTED] said:
> Is this your "stack trace"?
Close. What I'd really like is to get it to crash when it's running under
gdb, with a breakpoint on panic. Then, 'bt' to gdb at that point.
That gives the true call trace, plus line number information.
> 08297488: [<080697f0>] sig_handler_common_skas+0x90/0xe0
> 082974b8: [<08075e87>] sig_handler+0x17/0x20
> 08297508: [<0806b21f>] chan_interrupt+0xf/0x130
> 08297530: [<08064f70>] enable_mask+0x50/0x70
This tells me that chan_interrupt segfaulted, but not necessarily exactly
where, and a lot of the other stuff on the stack isn't in the true call
chain.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
