From: "Gross, Mark" <mark.gross@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] [RFC] Multithreaded core dump for 2.5.10-ia64 ke
Date: Thu, 06 Jun 2002 16:28:00 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905648@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905644@msgid-missing>
Good idea, I'll put the BUG_ON in.
I'll re-base to the updated 2.5.18 ia64 patches, that include
perfmon_itanium.h, and add the BUG_ON logic later today.
Thanks,
--mgross
(W) 503-712-8218
MS: JF1-05
2111 N.E. 25th Ave.
Hillsboro, OR 97124
> -----Original Message-----
> From: David Mosberger [mailto:davidm@napali.hpl.hp.com]
> Sent: Thursday, June 06, 2002 9:14 AM
> To: Gross, Mark
> Cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] [RFC] Multithreaded core dump for
> 2.5.10-ia64
> kernel.
>
>
> >>>>> 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:28 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
2002-06-06 16:28 ` Gross, Mark [this message]
2002-06-06 16:35 ` [Linux-ia64] [RFC] Multithreaded core dump for 2.5.10-ia64 ke 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-105590701905648@msgid-missing \
--to=mark.gross@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.