On Tuesday 07 August 2007, Kurt Miller wrote: > On Tuesday 07 August 2007 1:43:21 am J.C. Roberts wrote: > > I'm looking for all the needed steps to get firefox debug running > > in gdb. It's my first attempt at this and I've failed to the > > correct find the mozilla docs (assuming they exist) or details in > > the misc@, ports@ or tech@ archives. > > > > From what I've learned, you're supposed to use the following > > switches with the /usr/bin/firefox shell script. > > > > $ firefox -g > > > > You can be more explicit by naming the binary and the debugger. > > > > $ firefox -g /usr/local/mozilla-firefox/firefox-bin -d gdb > > > > The two are equivalent. > > > > Once inside gdb, I know you need to handle some signals. I've tried > > all combinations of the following signals and handling (nostop etc) > > without any luck: > > > > (gdb) handle SIG32 nostop noprint pass > > (gdb) handle SIG33 nostop noprint pass > > (gdb) handle SIGPIPE nostop noprint pass > > > > > > The problem I'm having is the gdb session just stops, without > > error, and firefox never actually loads. It never stops in the same > > place twice but it always stops. > > Hi, > > use 'set auto-solib-add off' to stop gdb from loading > symbols from all shared libs. then selectively load > shared lib symbols with 'shared libname' for placing > breakpoints or to get line numbers from 'bt'. > > this technique is also needed to debug OOo issues. > > -Kurt
Thank you, and Tobias, very much for the help... -But now I have a new problem (#$*&!); by just trying to debug firefox, I contracted Technical Tourette's Syndrome (fsck!) and my neighbors are probably wondering both what and why I keep shouting (5Hi7!). kind regards, jcr (p0wnD!)
