Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Stuart Brady <sdbrady@ntlworld.com>
To: linux-parisc@vger.kernel.org
Subject: Re: Segfault when ogg123 exits
Date: Tue, 11 Mar 2008 02:09:56 +0000	[thread overview]
Message-ID: <20080311020956.GA4155@miranda.arrow> (raw)
In-Reply-To: <119aab440803101739l778c3220w9102f6d814839694@mail.gmail.com>

On Mon, Mar 10, 2008 at 08:39:12PM -0400, Carlos O'Donell wrote:
> Can you distill this into a smaller testcase? Maybe a call to dlopen()
> to load a library that has a function called by timer_create?

I just ran ogg123 in gdb with a breakpoint set on timer_create(), and it
didn't get triggered, so timer_create() itself seems unlikely to be the
problem, but I can certainly try chopping libao down a bit.

BTW, this happens with both the OSS and ALSA plugins.

Side note: I've found that while running 'while (true); do true; done',
mmapped ALSA output seems to work!  If I drop the brackets, I just get 
noise -- presumably because it doesn't fork without them.
-- 
Stuart Brady

  reply	other threads:[~2008-03-11  2:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 21:31 Segfault when ogg123 exits Stuart Brady
2008-03-11  0:39 ` Carlos O'Donell
2008-03-11  2:09   ` Stuart Brady [this message]
2008-03-11 23:15     ` Carlos O'Donell

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=20080311020956.GA4155@miranda.arrow \
    --to=sdbrady@ntlworld.com \
    --cc=linux-parisc@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox