On 08 October 2009, Brice Goglin wrote with possible deletions: > You should start X normally,and then connect to the machine through ssh > and type gdp -p $(pidof X) > Then enter 'c' for continue in gdb, reproduce the bug, and get the > backtrace with 'bt full' in gdb. Ok. That's what I did. the results are attached. There are 3*3=9 files attached. Their names indicate the conditions under which the error showed up: - The files triggered.* com from a crash triggered by calling 'dmesg 9' as non-privoleged user. Yes, it is 'dmesg 9' not 'dmesg -n 9'. - The random.* files come from a crash that I did not consiously trigger. I bet I did, but I dont know why or how. - The normal.* files come from "normal" operation. I include them, because X seems to terminate with a SEGFAULT when the windowmanager disconnects and my session terminates. Suffices: - The files *.log.bz2 contain the logging of the gdb session. - The files *.dmesg.bz2 contain dmesg output from after the crash. - The files *.Xorg.0.log.bz2 contain Xorg.0.log from after the crash, at that point in thime had been renamed Xorg.0.log.old, because the X-server was restarted. I hope this helps you! Please ask in case you need further information!!! Kind regards, and thank you for looking into this! Stefan -- Stefan Klinger o/klettern /\/ bis zum send plaintext only - max size 32kB - no spam \ Abfallen http://stefan-klinger.de
Attachment:
normal.dmesg.bz2
Description: Binary data
BZh91AY&SY��G>