zapping crashed with SIGSEGV in free()

Bug #261377 reported by Bordi
8
Affects Status Importance Assigned to Milestone
zapping (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: zapping

.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/zapping
NonfreeKernelModules: nvidia
Package: zapping 0.10~cvs6-2
ProcAttrCurrent: unconfined
ProcCmdline: zapping
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: zapping
StacktraceTop:
 free () from /lib/tls/i686/cmov/libc.so.6
 g_free () from /usr/lib/libglib-2.0.so.0
 ?? ()
 zimage_unref ()
 ?? ()
Title: zapping crashed with SIGSEGV in free()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin mysql mythtv plugdev sambashare

Tags: apport-crash
Revision history for this message
Bordi (borderlinedancer) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:free () from /lib/tls/i686/cmov/libc.so.6
g_free () from /usr/lib/libglib-2.0.so.0
image_destroy (image=0x8d3dc10) at /build/buildd/zapping-0.10~cvs6/src/video_mem.c:122
zimage_unref (image=0x8d3dc10) at /build/buildd/zapping-0.10~cvs6/src/zimage.c:115
rebuild_buffer (pb=0x8d3a390, info=0x8a15c18) at /build/buildd/zapping-0.10~cvs6/src/capture.c:339

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in zapping:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in zapping:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) 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 zapping:
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.