On Mon, Jan 24, 2005 at 10:14:39AM +0100, Goswin von Brederlow wrote: > Hi, > > I wanted to track this bug but can't reproduce it on amd64: Right. I've been working with the submitter without much success. I asked for a shell account but that wasn't a possibility. Coredumps all indicate a stack smash. And the strace indicates some problem during initialization, before the call to init_X11.
I've given the submitter debugging instructions, involving a gdb trap on SIGFPE (though it will probably just show stack damage), and also the old stick-a-printf-after-reading-everything-in. Maybe there are uninitialized variables, or something.. I was looking for 2.4isms (like /proc/meminfo), but there appear to be 2.6isms instead.. Note that this is a sid-only bug. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
