Sean McNamara wrote: > Hi, > I hate to barge into this thread, but it seems you chose to quit the > debugger right here rather than printing a backtrace. That might have > been significantly more useful so we can get an idea of the context of > this function call (i.e. how the program got there). > > After pulseaudio gets a SIGSEGV, the first thing you should type into > gdb is `bt' (no quotes). Then you can quit. > > Sean > Thank you so much, Sean. It was oversight on my part, having not really done stack traces for any program before. Attaching the (hopefully correct) output. Methodology is as previously specified. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: gdbpulselog4.txt URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20090430/ab737283/attachment.txt> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: pulselog4.txt URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20090430/ab737283/attachment-0001.txt>
