From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [RFC] Multithreaded core dump for 2.5.10-ia64 kernel.
Date: Thu, 06 Jun 2002 16:13:45 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905647@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905644@msgid-missing>
>>>>> On Wed, 5 Jun 2002 14:33:12 -0700, "Gross, Mark" <mark.gross@intel.com> said:
Mark> I'm new to the stack unwinding thing WRT ia64 and would love
Mark> to get some feed back on my tweaks to process.c that collect
Mark> the register state data for the thread processes in the
Mark> crashing thread group.
It looks fine to me. One suggestion, however: it might be a good idea
to add a BUG_ON(task != current) statement to the dump_task_regs() and
dump_task_fpu() routines. This will stop folks from accidentally
trying to use unw_init_from_blocked_task() for the currently running
task.
--david
next prev parent reply other threads:[~2002-06-06 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 21:33 [Linux-ia64] [RFC] Multithreaded core dump for 2.5.10-ia64 kernel Gross, Mark
2002-06-06 16:13 ` David Mosberger [this message]
2002-06-06 16:28 ` [Linux-ia64] [RFC] Multithreaded core dump for 2.5.10-ia64 ke Gross, Mark
2002-06-06 16:35 ` 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=marc-linux-ia64-105590701905647@msgid-missing \
--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