Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 25541 - Running vlc produces "Segmentation fault"
Summary: Running vlc produces "Segmentation fault"
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Nick Hadaway
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-29 16:35 UTC by Steven Elling
Modified: 2003-08-13 19:49 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Elling 2003-07-29 16:35:29 UTC
This problem is occuring on Gentoo Linux but I suspect it might happen on other distros.  
The problem occurs when VLC is built using Gentoo's portage system, as well as, 
manually (i.e. configure ; make). 
 
Running vlc when the current directory is the vlc source directory works fine but if I cd to 
somewhere else and run vlc it produces a "Segmentation fault".  It doesn't matter if I try 
to run the vlc binary installed on the system by portage or the one in the source directory 
built manually.  It also doesn't matter which symbolic link (qvlc, gvlc, kvlc) I use to run 
the program 
 
Here is the gdb backtrace: 
 
(gdb) run 
Starting program: /usr/local/bin/vlc 
VideoLAN Client 0.6.0 Trevelyan 
[New Thread 16384 (LWP 20336)] 
 
Program received signal SIGSEGV, Segmentation fault. 
[Switching to Thread 16384 (LWP 20336)] 
0x40c09a66 in fREe () from /usr/kde/3.1/lib/libkdecore.so.4 
(gdb) bt 
#0  0x40c09a66 in fREe () from /usr/kde/3.1/lib/libkdecore.so.4 
#1  0x403ee2c0 in __libc_tsd_MALLOC_data () from /lib/libc.so.6 
(gdb) quit 
The program is running.  Exit anyway? (y or n) 
----- 
 
VLC was built from source using the following configure options: 
 
./configure --enable-svgalib --disable-fb --disable-dvd --disable-dvdread 
--disable-dvdplay --enable-alsa --enable-arts --enable-esd --disable-nls --disable-gtk2 
--enable-kde --enable-qt --enable-ncurses --disable-slp --enable-v4l --enable-faad 
--enable-a52 --enable-dvbpsi 
 
Using the '--disable-kde' option to configure does fix the problem, however, I no longer 
have the KDE interface, which is what I want to use.  Next, I figured I would use the QT 
interface instead but it produces a segmentation fault as well but only when I run VLC 
with the symbolic link qvlc. 
 
Here is the gdb backtrace from qvlc: 
 
(gdb) run 
Starting program: /usr/local/bin/qvlc 
VideoLAN Client 0.6.0 Trevelyan 
[New Thread 16384 (LWP 30780)] 
[New Thread 32769 (LWP 2910)] 
[New Thread 16386 (LWP 2911)] 
[New Thread 32771 (LWP 2923)] 
 
Program received signal SIGSEGV, Segmentation fault. 
[Switching to Thread 16384 (LWP 30780)] 
0x4033f56b in strlen () from /lib/libc.so.6 
(gdb) bt 
#0  0x4033f56b in strlen () from /lib/libc.so.6 
#1  0x40ac6aec in internalLatin1ToUnicode(char const*, unsigned*, unsigned) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#2  0x40ac73fd in QString::QString(char const*) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#3  0x4079456e in sm_performSaveYourself(QSessionManagerData*) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#4  0x40794382 in sm_saveYourselfCallback(_SmcConn*, void*, int, int, int, int) 
    () from /usr/qt/3/lib/libqt-mt.so.3 
#5  0x40efd401 in _SmcProcessMessage () from /usr/X11R6/lib/libSM.so.6 
#6  0x40f099df in IceProcessMessages () from /usr/X11R6/lib/libICE.so.6 
#7  0x40794e0a in QSmSocketReceiver::socketActivated(int) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#8  0x407950e2 in QSmSocketReceiver::qt_invoke(int, QUObject*) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#9  0x40849639 in QObject::activate_signal(QConnectionList*, QUObject*) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#10 0x40849715 in QObject::activate_signal(int, int) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#11 0x40b2b552 in QSocketNotifier::activated(int) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#12 0x40865cf0 in QSocketNotifier::event(QEvent*) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#13 0x407eb644 in QApplication::internalNotify(QObject*, QEvent*) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#14 0x407eabbb in QApplication::notify(QObject*, QEvent*) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#15 0x407c6338 in QEventLoop::activateSocketNotifiers() () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#16 0x407a3997 in QEventLoop::processEvents(unsigned) () 
   from /usr/qt/3/lib/libqt-mt.so.3 
#17 0x407ff466 in QEventLoop::enterLoop() () from /usr/qt/3/lib/libqt-mt.so.3 
#18 0x407ff308 in QEventLoop::exec() () from /usr/qt/3/lib/libqt-mt.so.3 
#19 0x407eb871 in QApplication::exec() () from /usr/qt/3/lib/libqt-mt.so.3 
#20 0x405ee4fe in Run (p_intf=0x81fd220) at modules/gui/qt/intf.cpp:115 
#21 0x0804ed79 in intf_RunThread (p_intf=0x40c4a128) 
    at src/interface/interface.c:124 
#22 0x0804e189 in VLC_AddIntf (i_object=0, psz_module=0x0, b_block=16981966) 
    at src/libvlc.c:609 
#23 0x0804a2af in main (i_argc=16981966, ppsz_argv=0x1031fce) at src/vlc.c:105 
#24 0x402dcdb4 in __libc_start_main () from /lib/libc.so.6 
(gdb) quit 
The program is running.  Exit anyway? (y or n) 
----- 
 
I am using KDE 3.1.2 and QT 3.1.2. 
 
This bug report has also been submitted to VideoLAN as bug ID 1055. 
 
http://bugzilla.videolan.org/cgi-bin/bugzilla/show_bug.cgi?id=1055
Comment 1 Nick Hadaway 2003-08-01 01:49:26 UTC
vlc-0.6.1 has been added to portage.  Please this new ebuild and let me know if you still have problems.  I have been able to utilize all interfaces wxvlc, vlc, gnome-vlc, svlc, qvlc, kvlc, and the mozilla plugin interface as well.
Comment 2 Steven Elling 2003-08-02 22:48:52 UTC
I've emerged vlc-0.6.1 (Portage Version 20030620).  I'll test it out and report back later. 
Comment 3 Steven Elling 2003-08-11 18:52:52 UTC
I have emerged vlc-0.6.1 and tested.  VLC now appears to be working properly 
using the KDE and QT interfaces. 
 
BTW: 'emerge -s vlc' indicates the version installed is "20030620" not "0.6.1". 
Comment 4 Nick Hadaway 2003-08-13 19:49:22 UTC
vlc-0.6.2 is now in portage as well.  Good to hear that things are working for you. :)