Re: [ReZound-users] rezound not working at all w/ Jack or OSS
Status: Beta
Brought to you by:
ddurham
From: Davy D. <ddu...@da...> - 2005-06-06 01:41:30
|
derek holzer wrote: > Hi Davy, > > Davy Durham wrote: > >> Well, if you get the same results, are you handy with a debugger, >> gdb? Run rezound in the debugger, then get it to crash. gdb will >> catch that, then do a 'bt' command to get a trace of the stack to try >> and figure out where it's dying. > > > I'm assuming that you patched the CVS tree with your alsa_crash.patch, > because when I tried to apply it to a fresh check-out, I got: > Yes I had.. I didn't realize that you were using a checkout from CVS. It should be fine.. it'll just ignore those changes since they're already in place. > > So here's the backtrace: > > Program received signal SIG32, Real-time event 32. > 0xb7f82ab3 in ?? () > (gdb) bt > #0 0xb7f82ab3 in ?? () > #1 0xb7f88b84 in ?? () > #2 0xbfffe9e0 in ?? () > #3 0xbfffea78 in ?? () > #4 0xb7f825db in ?? () > #5 0xbfffe9e0 in ?? () > #6 0x00000020 in ?? () > #7 0xbfffe9e0 in ?? () > (gdb) > > Not very verbose, is it? > d. > Yeah, gdb seems to catch those events, but they're not a problem. You may get a few of those at startup. Just repeatedly 'cont' (continue) the process after any "SIG32"s .. they're not a problem .. -- Davy |