On Tue, 2006-11-14 at 20:12 -0200, Otavio Salvador wrote:
Julien Cristau [EMAIL PROTECTED] writes:
In order to get a backtrace from the segfault, you need to run gdb on an
X server with debugging symbols enabled, which will then give a much
more informative backtrace.
The problem here
Michel Dänzer [EMAIL PROTECTED] writes:
On Tue, 2006-11-14 at 20:12 -0200, Otavio Salvador wrote:
Julien Cristau [EMAIL PROTECTED] writes:
In order to get a backtrace from the segfault, you need to run gdb on an
X server with debugging symbols enabled, which will then give a much
more
On Wed, 2006-11-15 at 09:10 -0200, Otavio Salvador wrote:
Michel Dänzer [EMAIL PROTECTED] writes:
On Tue, 2006-11-14 at 20:12 -0200, Otavio Salvador wrote:
Julien Cristau [EMAIL PROTECTED] writes:
In order to get a backtrace from the segfault, you need to run gdb on an
X server
Package: xserver-xorg-video-savage
Version: 1:2.1.2-1
Severity: important
KDM doesn't restart anymore when user logoff. I did a test and it
works fine wih 2.1.1-4 version so shouldn't be too difficult to
identify which change broke it.
If you wish any more testing, let me know.
,[ syslog
On Tue, Nov 14, 2006 at 10:59:38 -0200, Otavio Salvador wrote:
Package: xserver-xorg-video-savage
Version: 1:2.1.2-1
Severity: important
KDM doesn't restart anymore when user logoff. I did a test and it
works fine wih 2.1.1-4 version so shouldn't be too difficult to
identify which change
On Tue, Nov 14, 2006 at 15:19:35 -0200, Otavio Salvador wrote:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354]
1: [0xe420]
2: /usr/lib/xorg/modules/libramdac.so(xf86SetCursor+0x10b) [0xaf9ec6db]
3: /usr/lib/xorg/modules/libramdac.so [0xaf9ebd43]
4:
Julien Cristau [EMAIL PROTECTED] writes:
On Tue, Nov 14, 2006 at 15:19:35 -0200, Otavio Salvador wrote:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354]
1: [0xe420]
2: /usr/lib/xorg/modules/libramdac.so(xf86SetCursor+0x10b) [0xaf9ec6db]
3: /usr/lib/xorg/modules/libramdac.so
On Tue, Nov 14, 2006 at 17:16:27 -0200, Otavio Salvador wrote:
Julien Cristau [EMAIL PROTECTED] writes:
can you try rebuilding the X server with debugging symbols, and get a
more meaningful backtrace (probably by running gdb from the console, or
by getting a core file)?
Sure. Just
More info:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354]
1: [0xe420]
2: /usr/lib/xorg/modules/libramdac.so(xf86SetCursor+0x10b) [0xafa7e6db]
3: /usr/lib/xorg/modules/libramdac.so [0xafa7dd43]
4: /usr/bin/X(miPointerUpdate+0x167) [0x8112be7]
5: /usr/bin/X [0x8112cf9]
6: /usr/bin/X
Hi Otavio,
the core file you sent is not really usable as Xorg catches the SIGSEGV,
so the core file is only showing an abort.
In order to get a backtrace from the segfault, you need to run gdb on an
X server with debugging symbols enabled, which will then give a much
more informative backtrace.
Julien Cristau [EMAIL PROTECTED] writes:
Hi Otavio,
the core file you sent is not really usable as Xorg catches the SIGSEGV,
so the core file is only showing an abort.
In order to get a backtrace from the segfault, you need to run gdb on an
X server with debugging symbols enabled, which
11 matches
Mail list logo
