Bug 492315 - segfault in libc-2.9.so
Summary: segfault in libc-2.9.so
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 10
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-26 12:49 UTC by Mustafa Mehmed
Modified: 2009-04-18 17:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-18 17:32:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/messages (407.26 KB, text/plain)
2009-03-26 12:51 UTC, Mustafa Mehmed
no flags Details

Description Mustafa Mehmed 2009-03-26 12:49:21 UTC
Description of problem:
Trying to use Playlist -> Additional Sources > Shoutcast radio listings in VLC


Version-Release number of selected component (if applicable):
glibc-2.9-3.i686
vlc-0.9.8a-1.fc10.i386

How reproducible:
Always

Steps to Reproduce:
1. run vlc
2. select Playlist -> Additional Sources > Shoutcast radio listings
3. crash
  
Actual results:
VLC exits (crashes)

Expected results:
To see a shoutcast playlist

Additional info:
attached /var/log/messages

Comment 1 Mustafa Mehmed 2009-03-26 12:51:34 UTC
Created attachment 336791 [details]
/var/log/messages

Comment 2 Ulrich Drepper 2009-04-18 08:39:08 UTC
There is no way of saying what is going on.  The kernel message just means that the segfault happens while executing some code from glibc.  Not that the problem is in glibc.  It most likely isn't.

You'll have to provide much more detail.  Install the glibc-debuginfo package and run the program in question under gdb.

Comment 3 Mustafa Mehmed 2009-04-18 12:10:13 UTC
I now have:-

vlc-0.9.9.2.fc10.i386
glibc-2.9.3-i686

installed and there is no longer a problem.(In reply to comment #2)
> There is no way of saying what is going on.  The kernel message just means that
> the segfault happens while executing some code from glibc.  Not that the
> problem is in glibc.  It most likely isn't.
> 
> You'll have to provide much more detail.  Install the glibc-debuginfo package
> and run the program in question under gdb.

Comment 4 Ulrich Drepper 2009-04-18 17:32:26 UTC
Then whatever it was is handled.


Note You need to log in before you can comment on or make changes to this bug.