Bug#498397: vlc segfaults during test run in build process on mips resulting in build failure

[peter green]

package: vlc
severity: serious


vlc is run during it's own build process as a test and during that test 
it segfaults on mips and mipsel.  

I have tried moddin the wrapper script to run vlc under gdb and 
therefore get a backtrace (note: i'm using a libavcodec patched to fix 
the issue that was reported with it recently, thinking that would fix 
the segfault. It didn't help) but i'm not getting anything usefull out 
of it.


debian-mips:~/vlc-0.8.6.h# ./vlc --reset-plugins-cache -l -I rc vlc:quit
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "mips-linux-gnu"...
(gdb) run
Starting program: /root/vlc-0.8.6.h/.libs/lt-vlc --reset-plugins-cache 
-l -I rc
vlc:quit
[Thread debugging using libthread_db enabled]
VLC media player 0.8.6h Janus
starting VLC root wrapper...[New Thread 0x2b77c820 (LWP 3303)]
 using UID 0 (root)
***************************************
* Running VLC as root is discouraged. *
***************************************

 It is potentially dangerous, and might not even work properly.
  main                  main program
  help                  Help options
  mux_ts                TS muxer (libdvbpsi)
  theora                Theora video decoder
  theora                Theora video packetizer
  theora                Theora video encoder

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x2b77c820 (LWP 3303)]
0x2b00026c in ?? () from /usr/lib/libavcodec.so.51
(gdb) bt
#0  0x2b00026c in ?? () from /usr/lib/libavcodec.so.51
warning: GDB can't find the start of the function at 0x2b00026c.

    GDB is unable to find the start of the function at 0x2b00026c
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
    This problem is most likely caused by an invalid program counter or
stack pointer.
    However, if you think GDB should simply search farther back
from 0x2b00026c for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
#1  0x2b00026c in ?? () from /usr/lib/libavcodec.so.51
warning: GDB can't find the start of the function at 0x2b00026b.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)