From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: In-Kernel NaT consumption trap when debugging highly-parallel
Date: Thu, 25 Mar 2004 02:15:46 +0000 [thread overview]
Message-ID: <16482.16594.284650.930351@napali.hpl.hp.com> (raw)
In-Reply-To: <16482.12999.250663.921106@wombat.chubb.wattle.id.au>
>>>>> On Thu, 25 Mar 2004 12:15:51 +1100, Peter Chubb <peter@chubb.wattle.id.au> said:
Peter> Hi, I'm trying to debug a highly-threaded user-space program,
Peter> but gdb is triggering NaT consumption faults in the middle of
Peter> ptrace.
Peter> Does anyone have any good ideas on what could be going wrong,
Peter> and how to debug this?
Almost certainly a NULL-pointer dereference in the kernel. I thought
I had fixed a bug were unw_access_gr() was dereferencing a NULL
nat_addr some weeks ago, when I did the ptrace fixes. It looks like
that fix perhaps fell through the cracks or I decided no fixing was
needed after all. What kernel are you running and how easy is it to
reproduce the bug?
--david
next prev parent reply other threads:[~2004-03-25 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 1:15 In-Kernel NaT consumption trap when debugging highly-parallel Peter Chubb
2004-03-25 2:15 ` David Mosberger [this message]
2004-03-26 0:52 ` David Mosberger
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=16482.16594.284650.930351@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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