Ubuntu
jack package

[apport] jack crashed with SIGSEGV in free()

Bug #93225 reported by Forest Bond
2
Affects Status Importance Assigned to Milestone
jack (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: jack

This only occurs using Python 2.5. Forcing Python 2.4 (by changing the symlink in /usr/bin) made the problem go away.

ProblemType: Crash
Architecture: i386
Date: Sat Mar 17 17:17:22 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/jack
InterpreterPath: /usr/bin/python2.5
Package: jack 3.1.1+cvs20050801-14
PackageArchitecture: i386
ProcCmdline: /usr/bin/python /usr/bin/jack
ProcCwd: /home/fab/tmp/rip/jack-cb0c760e
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/fab/bin:/home/fab/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: jack
StacktraceTop:
 free () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux fab 2.6.20-11-lowlatency #2 SMP PREEMPT Thu Mar 15 08:06:06 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Forest Bond (forest-bond) wrote :
Sebastien Bacher (seb128)
Changed in jack:
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:free () from /lib/tls/i686/cmov/libc.so.6
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. The crash looks like a memory corruption. Could you try to get a valgrind log for it (you can follow the instructions from https://wiki.ubuntu.com/Valgrind for that)?

Changed in jack:
status: Unconfirmed → Needs Info
Revision history for this message
Forest Bond (forest-bond) wrote : Re: [Bug 93225] Re: [apport] jack crashed with SIGSEGV in free()

On Wed, Mar 21, 2007 at 10:14:05AM -0000, Sebastien Bacher wrote:
> Thanks for your bug report. The crash looks like a memory corruption.
> Could you try to get a valgrind log for it (you can follow the
> instructions from https://wiki.ubuntu.com/Valgrind for that)?

Funny thing ... I followed the instructions for running valgrind, but the crash
does not occur when valgrind is in use!

The crash is easily reproducible. When jack starts and the CD in the drive is
not in the CDDB database, jack asks if it should continue. It happens
consistently after answering yes to that question. I have not tried ripping a
CD that would be in the database; I suspect that jack would crash then, too.

I should remind you that switching back to Python 2.4 caused the problem to go
away.

-Forest

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

Can you get a valgrind log anyway? It can show errors without crash

Revision history for this message
Forest Bond (forest-bond) wrote :

Hi,

Sorry for the delay. Valgrind log attached.

-Forest

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for jack (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

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