From: jason.wessel@windriver•com (Jason Wessel)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 20/40] arm, kgdb: Add hook to catch an oops with debugger
Date: Thu, 14 Jan 2010 12:57:35 -0600 [thread overview]
Message-ID: <4B4F691F.3030500@windriver.com> (raw)
In-Reply-To: <20100114174821.GB21385@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
> On Thu, Jan 14, 2010 at 08:59:16AM -0600, Jason Wessel wrote:
>
>> Add in a low level hook to catch calls to die() in the debugger.
>>
>> After the debugger is done, the standard system rules will be in play
>> for the original exception.
>>
>> The kdb debugger wants a chance to catch these sorts of exceptions for
>> analysis.
>>
>
> NAK. I have a similar patch which implements the hook properly - but
> with one caveat. It needs a review to ensure that its safe to return
> from die(). Until that's established, this patch can not be merged.
>
I dropped the patch which you NAK'ed from the series.
As for your included patch, I will try it out against the various
regression tests I have, which exercise the oops and exception paths.
> Please also ensure that the linux-arm-kernel list is copied with ARM
> patches.
>
>
Check.
Thanks,
Jason.
next prev parent reply other threads:[~2010-01-14 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1263481176-1897-1-git-send-email-jason.wessel@windriver.com>
[not found] ` <1263481176-1897-21-git-send-email-jason.wessel@windriver.com>
2010-01-14 17:48 ` [PATCH 20/40] arm,kgdb: Add hook to catch an oops with debugger Russell King - ARM Linux
2010-01-14 18:57 ` Jason Wessel [this message]
2010-01-14 20:29 ` [PATCH 20/40] arm, kgdb: " Jason Wessel
2010-01-14 20:46 ` [PATCH 20/40] arm,kgdb: " Russell King - ARM Linux
2010-01-18 14:30 ` Jason Wessel
2010-01-20 16:03 ` Russell King - ARM Linux
2010-01-20 17:01 ` Jason Wessel
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=4B4F691F.3030500@windriver.com \
--to=jason.wessel@windriver$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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