libgl1_mesa_dri segmentation fault in _mesa_get_teximage

Bug #79452 reported by Sebastien SOILEN
2
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: libgl1-mesa-dri

Hi!

I got a segmentation fault during start of the stellarium program.
I reproduced the same bug (same function, same moment) with the SVN last version of this program. The segmentation fault occurs inside the mesa dri library.

NOTE: The bug doesn't occur when I use the vesa driver with my xserver x.org .

Here is the backtrace:

#0 0x00000000 in ?? ()
#1 0xb6dfaf5f in _mesa_get_teximage () from /usr/lib/dri/unichrome_dri.so
#2 0xb6deedbe in _mesa_GetTexImage () from /usr/lib/dri/unichrome_dri.so
#3 0xb7e3c456 in glGetTexImage () from /usr/lib/libGL.so.1
#4 0x081bda53 in STexture::getAverageLuminance (this=0x8b54b20)
at STexture.cpp:56
#5 0x081a51d2 in ManagedSTexture::getAverageLuminance (this=0x8b54b20)
at StelTextureMgr.cpp:76
#6 0x081b510c in MilkyWay::setTexture (this=0x8b54a88, tex_file=@0xbfb5c900)
at MilkyWay.cpp:60
#7 0x081b5172 in MilkyWay::init (this=0x8b54e08, conf=@0xbfb5cb34,
lb=@0xbfb5caec) at MilkyWay.cpp:48
#8 0x08119897 in StelApp::init (this=0xbfb5ccb4) at StelApp.cpp:271
#9 0x0811a91a in StelApp (this=0xbfb5ccb4, CDIR=@0x83d6c34, LDIR=@0x83d6c38,
DATA_ROOT=@0x83d6c3c) at StelApp.cpp:74
#10 0x080f23c6 in main (argc=Cannot access memory at address 0x0
) at main.cpp:247

If I put a breakpoint at the entry point of the _mesa_get_teximage function, I get
the segmentation fault at the following step of execution:

Breakpoint 2, 0xb6e72d78 in _mesa_get_teximage ()
from /usr/lib/dri/unichrome_dri.so
(gdb) step
Single stepping until exit from function _mesa_get_teximage,
which has no line number information.

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()

My current config is:
Ubuntu 6.10
graphic card VIA KM400 with the last version of the ubuntu driver (xorg-video-via 1.0.2.1)
libgl1-mesa-dri 6.5.1~20060817 (last version)

Sébastien SOILEN

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. Could you try to get a debug backtrace (https://wiki.ubuntu.com/DebuggingProgramCrash)?

Changed in mesa:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Sebastien SOILEN (sebastien-soilen) wrote : Re: [Bug 79452] Re: libgl1_mesa_dri segmentation fault
Download full text (6.8 KiB)

Hello,

here is the debug backtrace. If you need further details about
the bug, don't hesitate to ask me.

Regards,

Sebastien

2007/3/5, Sebastien Bacher <email address hidden>:
>
> Thank you for your bug. Could you try to get a debug backtrace
> (https://wiki.ubuntu.com/DebuggingProgramCrash)?
>
> ** Changed in: mesa (Ubuntu)
> Importance: Undecided => Medium
> Status: Unconfirmed => Needs Info
>
> --
> libgl1_mesa_dri segmentation fault
> https://launchpad.net/bugs/79452
>

--
============================

SOILEN Sébastien
<email address hidden>

GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/stellarium
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1216018240 (LWP 4855)]
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
 -------------------------------------------------------
[ This is Stellarium 0.8.1 - http://www.stellarium.org ]
[ Copyright (C) 2000-2006 Fabien Chereau et al ]
 -------------------------------------------------------
(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)
[New Thread -1216320608 (LWP 4858)]
(no debugging symbols found)
(no debugging symbols found)
libGL warning: 3D driver claims to not support visual 0x46
(no debugging symbols found)
Application locale is system
Localizing TUI for locale: system
Loading Solar System data...(loaded)
Loading location: "Paris", on Earth (landscape is: "guereins")
Loading Hipparcos star data...(118217 stars loaded [2200 dropped]).
Loading Hipparcos double stars...(8824 stars loaded)
Loading Hipparcos periodic variable stars...(1930 stars loaded)
Load star names from...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote : Re: libgl1_mesa_dri segmentation fault

Thank you for the update

Changed in mesa:
status: Needs Info → Unconfirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Could you please try with Feisty, which has a newer mesa.

Changed in mesa:
status: Unconfirmed → Needs Info
Revision history for this message
Sebastien SOILEN (sebastien-soilen) wrote :
Download full text (4.8 KiB)

The problem stills occurs with Feisty

Here is the backtrace:

 gdb stellarium
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/stellarium
(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)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1216764208 (LWP 14071)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(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)
 -------------------------------------------------------
[ This is Stellarium 0.8.2 - http://www.stellarium.org ]
[ Copyright (C) 2000-2006 Fabien Chereau et al ]
 -------------------------------------------------------
Attempting to use an existing older config file.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1216935024 (LWP 14075)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Application locale is fr_FR
Localizing TUI for locale: fr_FR
Loading Solar System data...(loaded)
Loading location: "barcelona", on Earth (landscape is: "guereins")
Loading Hipparcos star data...(118217 stars loaded [2200 dropped]).
Loading Hipparcos double stars...(8824 stars loaded)
Loading Hipparcos periodic variable stars...(1930 stars loaded)
Load star names from /usr/share/stellarium/data/sky_cultures/western/star_names.fab
Loading NGC data... (13226 items loaded [3175 dropped])

...no position data for Barnard's galaxy
...no position data for Papillon
...no position data for γ Cas nebulaLoading NGC name data...( 225 names loaded)
Loading Nebula Textures...(75 textures loaded)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1216764208 (LWP 14071)]
0x00000000 in ?? ()
(gdb) backtrace
#0 0x00000000 in ?? ()
#1 0xb6e1845b in _mesa_get_teximage () from /usr/lib/dri/unichrome_dri.so
#2 0xb6e0d3d0 in _mesa_GetTexImage () from /usr/lib/dri/unichrome_dri.so
#3 0x080b1098 in ?? ()
#4...

Read more...

Changed in mesa:
status: Incomplete → New
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Thanks for your bug report. Does this still happen in Gutsy or Hardy? If so, please attach your Xorg.0.log and xorg.conf.

Changed in mesa:
assignee: nobody → tormodvolden
status: New → Incomplete
Revision history for this message
tw3k (tw3k-net) wrote :

I upgraded to Hardy last night and the Unichrome driver is working much better for me now. The machine will still lock up ocasionally but glxinfo no longer segfaults. If I naorrow it down further I'll attach a backtrace.

Good work!

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

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in mesa:
assignee: tormodvolden → nobody
status: Incomplete → Invalid
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.