glcells crashed with SIGSEGV in malloc()

Bug #473348 reported by serge8383
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xscreensaver (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: xscreensaver

htt

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Nov 3 15:03:24 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/xscreensaver/glcells
NonfreeKernelModules: wl
Package: xscreensaver-gl 5.08-0ubuntu5
ProcCmdline: glcells -root
ProcEnviron:
 PATH=(custom, user)
 LANG=es_CO.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x4bc090: cmp 0xc(%eax),%edi
 PC (0x004bc090) ok
 source "0xc(%eax)" (0x3f80000c) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xscreensaver
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
Title: glcells crashed with SIGSEGV in malloc()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare

Revision history for this message
serge8383 (serge8383) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:malloc_consolidate (av=<value optimized out>)
_int_malloc (av=<value optimized out>,
*__GI___libc_malloc (bytes=8280) at malloc.c:3638
clone_Object (obj=0x894d108) at glcells.c:411
draw_cell (st=<value optimized out>, shape=0)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in xscreensaver (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Kees Cook (kees)
security vulnerability: yes → no
visibility: private → public
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.