[vlc-devel] Bug#443660: New test case for #443660

[Pierre Habouzit]

On Sun, Dec 16, 2007 at 01:30:39PM +0000, Rémi Denis-Courmont wrote:
> Le Sunday 16 December 2007 12:58:16 Pierre Habouzit, vous avez écrit :
> > notfound 443660 2.7-4
> > thanks
> >
> > On Sat, Dec 15, 2007 at 07:35:36PM +0000, Rémi Denis-Courmont wrote:
> > > found 443660 2.7-4
> > > thanks
> > >
> > > 	Hello,
> > >
> > > Seems like the original test case does not crash anymore. I still have
> > > problems with this one new though - it crashes pseudorandomly (about 10%
> > > crashes here). Unfortunately, I have not been able to reproduce the
> > > problem under a debugger.
> > >
> > > Interestingly, I once had the crash with the first error message in C
> > > locale:
> >
> >   I completely fail to see why it's the same bug, in fact I'm almost
> > sure it's not. And without a backtrace I'm unsure what we can do about
> > it. Please open a new bug instead of diverting old bugs from their
> > purpose.
> 
> Connexion terminée par
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x86bd0b90 (LWP 10614)]
> 0xb7e599d8 in strcmp () from /lib/i686/cmov/libc.so.6
> (gdb) bt
> #0  0xb7e599d8 in strcmp () from /lib/i686/cmov/libc.so.6
> #1  0xb7e0d473 in _nl_find_msg () from /lib/i686/cmov/libc.so.6
> #2  0xb7e0e122 in __dcigettext () from /lib/i686/cmov/libc.so.6
> #3  0xb7e0ceb3 in dcgettext () from /lib/i686/cmov/libc.so.6
> #4  0xb7e59ee9 in strerror_r () from /lib/i686/cmov/libc.so.6
> #5  0xb7e27c9f in vfprintf () from /lib/i686/cmov/libc.so.6
> #6  0xb7e4a874 in vsnprintf () from /lib/i686/cmov/libc.so.6
> #7  0xb7e2f1d5 in snprintf () from /lib/i686/cmov/libc.so.6
> #8  0x080485f0 in run ()
> #9  0xb7f3a4fb in start_thread () from /lib/i686/cmov/libpthread.so.0
> #10 0xb7ebe60e in clone () from /lib/i686/cmov/libc.so.6
> 
> Looks like exactly the same problem to me.

  The trace is the same indeed, could you provide a valgrind trace ? I'm
completely unable to reproduce the bug with a glibc 2.7-4. Are you sure
youre libc6-686 is a 2.7-4 as well ?

  But I looked at the code, the section that does the realloc that was
responsible for the crash before is properly guarded by mutexes now, so
it's definitely (if there still is a crash which atm have no proof
about) not occurring at the same place. Hence the valgrind trace that
tells line numbers would help a lot.

-- 
·O·  Pierre Habouzit
··O                                                madcoder at debian.org
OOO                                                http://www.madism.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20071216/18d88adf/attachment.sig>