double-free now fatal ? (Re: Bug#304711: soundtracker: crash on startup)

[Junichi Uekawa <dancer@netfort.gr.jp>]

> When I try to run soundtracker, I get:
> 
> > soundtracker
> *** glibc detected *** free(): invalid pointer: 0xbffff150 ***
> Aborted (core dumped)
> 
This is due to using a newer glibc that gives out core on double-free.
I'm ccing debian-glibc to make sure; is this the case?


In my environment, it's just a warning:

$ LC_ALL=C LANG=C soundtracker
free(): invalid pointer 0xbfefa420!

** WARNING **: error subscribing sequencer port (Invalid argument)



> When I examine the dumped core, I get:
> 
> (gdb) bt
> #0  0xb78da687 in raise () from /lib/tls/libc.so.6
> #1  0xb78dbde7 in abort () from /lib/tls/libc.so.6
> #2  0xb790dc49 in __fsetlocking () from /lib/tls/libc.so.6
> #3  0xb7916676 in mallopt () from /lib/tls/libc.so.6
> #4  0xb791535d in mallopt () from /lib/tls/libc.so.6
> #5  0xb79140cb in free () from /lib/tls/libc.so.6
> #6  0xb7a5980f in snd_seq_port_subscribe_free (obj=0x0) at seq.c:2313
> #7  0x0808b2ac in midi_init ()
> #8  0x0806cffc in main ()
> 
> (I saw the other crash bug report, but wasn't sure it is the same, so
> made a new one.)

The other crash report only reproduces in powerpc, which probably
couldn't detect the double free and did something nasty.

Apparently this double-free bug needs to be fixed after all.





regards,
	junichi