http://bugs.freedesktop.org/show_bug.cgi?id=24303
--- Comment #4 from Zhivko <[email protected]> 2009-10-05 10:18:41 PST --- (In reply to comment #3) > Can you get a proper backtrace of the crash with gdb? Also, can you bisect > what commit caused the problem? > Should I do a gdb on /usr/bin/X ? I haven't done this before. If I do so I get ====== Starting program: /usr/bin/X (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Program exited with code 01. (gdb) [K(gdb) Hangup detected on fd 0 Error detected on fd 0 error detected on stdin ====== I think the last 3 rows are generated when X restarts when I maximized a window. But it it could be a standard gdb output whenever X crashes and gdb is stopped. Not sure I'm doing it properly. As far as the commits, I really don't know what could have caused it, I mean, I'm not an expert :( -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
