segfault in XMesaMakeCurrent2

Bug #65942 reported by Tormod Volden
2
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
New
Undecided
Unassigned

Bug Description

Not sure what package this belongs to, but libGLcore.so belongs to xserver-xorg-core which is built from xorg-server. I am using the proprietary fglrx driver on an ATI X1300 (RV515).

Revision history for this message
Tormod Volden (tormodvolden) wrote :
Revision history for this message
Tormod Volden (tormodvolden) wrote :
Revision history for this message
Tormod Volden (tormodvolden) wrote :

It crashed again, but not in the same function from what I can see:

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c38e1]
1: [0xffffe420]
2: /usr/lib/xorg/modules/extensions/libglx.so [0xb7c1b946]
3: /usr/lib/xorg/modules/extensions/libglx.so(__glXleaveServer+0x22) [0xb7bf7c62]
4: /usr/lib/xorg/modules/extensions/libglx.so [0xb7bf82fe]
5: /usr/X11R6/bin/X(Dispatch+0x18f) [0x808690f]
6: /usr/X11R6/bin/X(main+0x485) [0x806e715]
7: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d368cc]
8: /usr/X11R6/bin/X(FontFileCompleteXLFD+0xa1) [0x806da51]

Fatal server error:
Caught signal 11. Server aborting

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I guess the frame 1 at 0xffffe420 which appears in both backtraces is from the crash handling?

Is it interesting that both backtraces start in FontFileCompleteXLFD ?

I have installed xserver-xorg-core-dbgsym and set this in xorg.conf:
Option "NoTrapSignals" "true"
Just have to wait for the next crash :)

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Just saw that the second backtrace is the same as in bug #60288. Someone competent has to decide if this is a separate bug or not.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.