From: Paul Davis <paul@linuxaudiosystems.com>
To: alsa-devel@lists.sourceforge.net
Subject: crash trace under gdb
Date: Fri, 9 May 2003 10:05:36 -0400 [thread overview]
Message-ID: <200305091405.h49E5af01571@linuxaudiosystems.com> (raw)
well, it appears that the lock up occurs in a call to
__read_lock_failed, with the PC toward the end of __kill_fasync. it
alternates between two address that are both within that function,
different by 9 bytes.
ctrl-alt-sysreq couldn't provide a trace more than 1 call back. not
sure why.
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
next reply other threads:[~2003-05-09 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 14:05 Paul Davis [this message]
2003-05-09 14:23 ` crash trace under gdb Takashi Iwai
2003-05-09 14:31 ` Paul Davis
2003-05-09 15:39 ` Paul Davis
[not found] ` <20030509153542.E0A9D14CE5@Cantor.suse.de>
2003-05-09 15:41 ` Takashi Iwai
2003-05-09 17:28 ` Abramo Bagnara
2003-05-09 17:48 ` Paul Davis
2003-05-09 17:57 ` Abramo Bagnara
2003-05-09 18:11 ` Paul Davis
[not found] ` <20030509174418.C8F9714CE0@Cantor.suse.de>
2003-05-09 17:49 ` Takashi Iwai
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=200305091405.h49E5af01571@linuxaudiosystems.com \
--to=paul@linuxaudiosystems.com \
--cc=alsa-devel@lists.sourceforge.net \
/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