On Tue, 2004-01-13 at 01:01, Stephen Waters wrote: > On Mon, 2004-01-12 at 16:32, Michel DÃnzer wrote: > > On Mon, 2004-01-12 at 20:36, Xavier Hienne wrote: > > > Stephen Waters wrote: > > > > I'm attaching Xfree86 logs for 2.6.1-bk1-amd64 and Debian sid's 32-bit > > > > 2.6.0-k7-smp. > > > > > > > > I still get the segfaults with amd64, but I haven't managed an strace. > > > > Stupid forking keeps kill my strace! :) > > > > What forking, BTW? The X server doesn't fork, does it? > > I can't figure out why else strace would just stop logging and exit > normally... > > here's my workflow: > 1) /etc/init.d/gdm restart > 2) ctrl+alt+f1 to get back to terminal > 3) ps x |grep X > 4) strace -p pid_of_X > 5) alt+f7 > 6) log into gdm > 7) <crash> > 8) back to VT1 where I notice that strace exited normally without any > useful information leading me to believe that it exits at login due to > some forking thing.
Not sure, the VT switch involves a signal, maybe that's it. > Is there something smarter I should do? The best thing is to log in remotely and attach gdb to the server. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Software libre enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
