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.
On Wed, Mar 21, 2007 at 10:14:05AM -0000, Sebastien Bacher wrote: /wiki.ubuntu. com/Valgrind for that)?
> 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:/
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