All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@manicmethod.com>
To: Vikram Noel Ambrose <noel.ambrose@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: xine_init() causes segfault in libselinux
Date: Thu, 02 Apr 2009 16:12:09 -0400	[thread overview]
Message-ID: <49D51C19.1000105@manicmethod.com> (raw)
In-Reply-To: <49D00BEB.2030000@gmail.com>

Vikram Noel Ambrose wrote:
> Hello Everyone,
> 
> I've managed to find a repeatable segfault scenario with some very basic 
> libxine code.
> 
> libxine if anyone doesnt know is a very popular audio backend for many 
> userspace applications in KDE and Gnome.
> 
> Here is the code: http://en.pastebin.ca/1376316
> 
> The code basically opens a file stream with no Audio or Video drivers, 
> and just reads the meta data from the file (title information), and then 
> quits.
> 
> A gdb backtrace and valgrind have led me to believe there is a fault in 
> libselinux.
> 
> Though this could very possibly be a fault in libxine, I'd have thought 
> libselinux would be more resilient to such issues. Especially since 
> glibc didnt complain.
> 
> If you would like to run this test code, simply install xine-lib-devel 
> and then compile the test program.
> 
> $ gcc -lxine -g test.c
> $ ./a.out
> 
> I'm using an up-to-date FC10 x86_64 installation. 
> 2.6.27.19-170.2.35.fc10.x86_64
> 
> 

I can't reproduce this on an x86 F10 install with either the latest libselinux 
or trunk libselinux. Can you try installing a libselinux from trunk with DEBUG=1 
make flag so the backtrace will give more information?

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

      parent reply	other threads:[~2009-04-02 20:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30  0:01 xine_init() causes segfault in libselinux Vikram Noel Ambrose
2009-03-30 11:46 ` Daniel J Walsh
2009-04-02 20:12 ` Joshua Brindle [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49D51C19.1000105@manicmethod.com \
    --to=method@manicmethod.com \
    --cc=noel.ambrose@gmail.com \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.