Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@systemhalted.org>
To: "Stuart Brady" <sdbrady@ntlworld.com>
Cc: linux-parisc@vger.kernel.org
Subject: Re: Segfault when ogg123 exits
Date: Mon, 10 Mar 2008 20:39:12 -0400	[thread overview]
Message-ID: <119aab440803101739l778c3220w9102f6d814839694@mail.gmail.com> (raw)
In-Reply-To: <20080305213128.GA27120@miranda.arrow>

On Wed, Mar 5, 2008 at 5:31 PM, Stuart Brady <sdbrady@ntlworld.com> wrote:
>  It seems ogg123 segfaults when it finishes playing.  Note that I'm not
>  pressing ^C -- I'm not even sure whether the "^C bug" is still around.
>  From the backtrace, it looks like this may well be the same problem I
>  reported with SDL_Quit() and timer_create():
>
>  #0  0x00000000 in ?? ()
>  #1  0x400a7aac in _dl_close_worker () from /lib/ld.so.1
>  #2  0x400a7c08 in _dl_close () from /lib/ld.so.1
>  #3  0x400190dc in dlclose_doit () from /lib/libdl.so.2
>  #4  0x400a1834 in _dl_catch_error () from /lib/ld.so.1
>  #5  0x40019590 in _dlerror_run () from /lib/libdl.so.2
>  #6  0x40019118 in dlclose () from /lib/libdl.so.2
>  #7  0x402f9ffc in ao_shutdown () from /usr/lib/libao.so.2
>  #8  0x40c57bd4 in exit () from /lib/libc.so.6
>  #9  0x000182fc in main ()
>
>  Would any glibc hackers feel like taking a closer look at this?

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?

Cheers,
Carlos.

  reply	other threads:[~2008-03-11  0:39 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 [this message]
2008-03-11  2:09   ` Stuart Brady
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=119aab440803101739l778c3220w9102f6d814839694@mail.gmail.com \
    --to=carlos@systemhalted.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=sdbrady@ntlworld.com \
    /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