glxgears crashed with SIGSEGV in calloc()

Bug #428909 reported by Angel Guzman Maeso
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Just running the app, it crash.

ProblemType: Crash
Architecture: i386
Date: Sun Sep 13 17:18:07 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/glxgears
MachineType: Hewlett-Packard Compaq Presario C700 Notebook PC
Package: mesa-utils 7.6.0~git20090817.7c422387-0ubuntu3
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: root=UUID=1099c101-1d60-457b-b823-c27423ff1035 ro splash
ProcCmdline: glxgears
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_ES.UTF-8
 LANGUAGE=es_ES.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3
 libdrm2 2.4.13-1ubuntu1
 xserver-xorg-video-intel 2:2.8.1-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu1
SegvAnalysis:
 Segfault happened at: 0xc84d09 <calloc+105>: cmpxchg %edx,(%esi)
 PC (0x00c84d09) ok
 source "%edx" ok
 destination "(%esi)" (0x3b31303d) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: mesa
StacktraceTop:
 calloc () from /lib/libc.so.6
 _nv000136gl () from /usr/lib/libGLcore.so.1
 ?? ()
 ?? ()
 ?? ()
Title: glxgears crashed with SIGSEGV in calloc()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video
XorgConf: Error: [Errno 2] No existe el fichero ó directorio: '/etc/X11/xorg.conf'
dmi.bios.date: 04/29/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.33
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 30D9
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 83.21
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.33:bd04/29/2008:svnHewlett-Packard:pnCompaqPresarioC700NotebookPC:pvrF.33:rvnHewlett-Packard:rn30D9:rvr83.21:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Compaq Presario C700 Notebook PC
dmi.product.version: F.33
dmi.sys.vendor: Hewlett-Packard
fglrx: Not loaded
glxinfo: Error: command ['glxinfo'] failed with exit code -11:
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-10-generic

Revision history for this message
Angel Guzman Maeso (shakaran) wrote :
visibility: private → public
Bryce Harrington (bryce)
tags: added: crash
Changed in mesa (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__libc_calloc (n=1, elem_size=52) at malloc.c:4019
_nv000136gl () from /usr/lib/libGLcore.so.1
?? ()
_dl_init (main_map=0x34, argc=<value optimized out>,
_dl_start_user () from /lib/ld-linux.so.2

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in mesa (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Mike Pontillo (mpontillo) wrote :

This appears to be an exact duplicate of the bug 429794, which I just filed.

From the stack trace, I'm wondering if this is a bug in the nvidia-glx driver:

$ dpkg -S /usr/lib/libGLcore.so.1
nvidia-glx-185: /usr/lib/libGLcore.so.1

... but I can't select the nvidia-graphics-drivers-185 package, so I'm not sure if the correct people have visibility.

Revision history for this message
Mike Pontillo (mpontillo) wrote :

Ah, since this bug was reported on an Intel chipset and mine is on nvidia, it seems the theory that this is an nvidia-glx bug is not correct.

It seems like a calloc() call for 52 bytes should *really* not fail. Maybe this is a libc6 bug?

$ apt-cache policy libc6
libc6:
  Installed: 2.10.1-0ubuntu11
  Candidate: 2.10.1-0ubuntu11
  Version table:
 *** 2.10.1-0ubuntu11 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

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.