Bug#406044: Same Problem with gdm

2007-01-21 Thread Michel Dänzer 
On Sat, 2007-01-20 at 19:41 +0100, Erik Tews wrote:
 
 I am using gdm and a gnome-desktop afterwards. Sometimes my x-server
 crashes (about 2 times a day or so). I get the same backtrace:
 
 Backtrace:
 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354]
 1: [0xb7f31420]
 2: /usr/bin/X(Dispatch+0x81) [0x8086b91]
 3: /usr/bin/X(main+0x489) [0x806e699]
 4: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7d24ea8]
 5: /usr/bin/X(FontFileCompleteXLFD+0xa9) [0x806d9d1]
 
 But I don't know how to reproduce it exactly. Can I help you with
 debugging?

In addition to the information requested by Sune, it would be useful to
get a backtrace from gdb attached to the X server (only possible from a
remote login), ideally with the X server and drivers rebuilt with
debugging symbols.


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer

Bug#406044: Same Problem with gdm

2007-01-21 Thread Erik Tews 
Am Sonntag, den 21.01.2007, 12:55 +0100 schrieb Michel Dänzer:
 On Sat, 2007-01-20 at 19:41 +0100, Erik Tews wrote:
  
  I am using gdm and a gnome-desktop afterwards. Sometimes my x-server
  crashes (about 2 times a day or so). I get the same backtrace:
  
  Backtrace:
  0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354]
  1: [0xb7f31420]
  2: /usr/bin/X(Dispatch+0x81) [0x8086b91]
  3: /usr/bin/X(main+0x489) [0x806e699]
  4: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7d24ea8]
  5: /usr/bin/X(FontFileCompleteXLFD+0xa9) [0x806d9d1]
  
  But I don't know how to reproduce it exactly. Can I help you with
  debugging?
 
 In addition to the information requested by Sune, it would be useful to
 get a backtrace from gdb attached to the X server (only possible from a
 remote login), ideally with the X server and drivers rebuilt with
 debugging symbols.

Having a remote login on the machine is not so easy, while the X server
is crashing.

I think I can recompile the debian package with debugging informations.
Will the crash handler then give more usefull informations?

One additional update. This seems to happen only when I am typing
something on my keyboard. The server never crashed yet when the computer
was just ideling without me.


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

Bug#406044: Same Problem with gdm

2007-01-21 Thread Michel Dänzer 
On Sun, 2007-01-21 at 13:53 +0100, Erik Tews wrote:
 Am Sonntag, den 21.01.2007, 12:55 +0100 schrieb Michel Dänzer:
  
  In addition to the information requested by Sune, it would be useful to
  get a backtrace from gdb attached to the X server (only possible from a
  remote login), ideally with the X server and drivers rebuilt with
  debugging symbols.
 
 Having a remote login on the machine is not so easy, while the X server
 is crashing.

Yeah, I'm afraid you'd have to keep a remote login running gdb attached
to the X server whenever possible.

 I think I can recompile the debian package with debugging informations.
 Will the crash handler then give more usefull informations?

Unfortunately not, in my experience.


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer

Bug#406044: Same Problem with gdm

2007-01-20 Thread Erik Tews 
Hi

I am using gdm and a gnome-desktop afterwards. Sometimes my x-server
crashes (about 2 times a day or so). I get the same backtrace:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354]
1: [0xb7f31420]
2: /usr/bin/X(Dispatch+0x81) [0x8086b91]
3: /usr/bin/X(main+0x489) [0x806e699]
4: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7d24ea8]
5: /usr/bin/X(FontFileCompleteXLFD+0xa9) [0x806d9d1]

But I don't know how to reproduce it exactly. Can I help you with
debugging?


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil