On Sat, 2004-02-07 at 04:53, Michel DÃnzer wrote: > On Sat, 2004-02-07 at 03:55, Stephen Waters wrote: > > On Mon, 2004-01-12 at 18:09, Michel DÃnzer wrote: > > > > > > The best thing is to log in remotely and attach gdb to the server. > > > > I just tried this. Here's what happens: > > > > # gdb > > (gdb) attach $pid_of_X > > Loading Symbols... blah blah > > FWIW, when I attach gdb to a process, I usually start it with the > corresponding binary, e.g. > > gdb XFree86
I tried that, but X detaches itself from the running gdb session whenever I start a WM so I have to use "attach PID". I have to start a WM, because the problem doesn't manifest itself until I start one. Enlightenment is a good example b/c of its rich feature set... really taxes the graphics libs, etc. But, even twm will crash with some effort so I don't think it's localized to Enlightenment. > > (gdb) continue > > Segmentation Fault > > Is this gdb segfaulting? If so, that's a gdb bug which should be > reported. It could be a kernel bug... there's a patch between 2.6.0 and 2.6.3-rc1 which fixes some gdb problem on amd64. Will let you and/or gdb team know if I manage to get 2.6.3-rc1 (or higher) up and running. -s
signature.asc
Description: This is a digitally signed message part
