From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Jeffrey Merkey <jeffmerkey@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, Jason@zx2c4.com,
aconole@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
andriy.shevchenko@linux.intel.com, linus.walleij@linaro.org,
nicolas.iooss_linux@m4x.org, pmladek@suse.com, tj@kernel.org
Subject: Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options
Date: Tue, 2 Feb 2016 19:40:48 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.20.1602021932550.2715@eddie.linux-mips.org> (raw)
In-Reply-To: <CA+ekxPUTxpXbWtCWoYe7EqqZO2Ey2ko9YHivwQe3nApninHCvA@mail.gmail.com>
On Mon, 1 Feb 2016, Jeffrey Merkey wrote:
> If a debugger is loaded it will not crash, just enter the debugger.
> But yes, it will int3 if set and no debugger has been loaded to handle
> the int3 condition. Hmmm. Maybe its better just to skip calling
> pr_emerg and put this logic as a single call somewhere else.
What's the point? If you have a debugger loaded, then surely you can
just set a breakpoint anywhere you like using whatever user interface the
debugger provides for setting breakpoints. You can actually set any
number of software breakpoints you like wherever you like, depending on
what you actually want to debug. I fail to see why it would have to be
prearranged within the kernel -- do you have a configuration where you run
the kernel from ROM by any chance?
Maciej
next prev parent reply other threads:[~2016-02-02 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 23:35 [PATCH v4 1/4] Add BUG_XX() debugging options Jeffrey Merkey
2016-02-01 23:35 ` [PATCH v4 2/4] Add WARN_XX() " Jeffrey Merkey
2016-02-01 23:35 ` [PATCH v4 3/4] Add BUG_XX() and " Jeffrey Merkey
2016-02-01 23:35 ` [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options Jeffrey Merkey
2016-02-02 1:58 ` Steven Rostedt
2016-02-02 2:01 ` Jeffrey Merkey
2016-02-02 19:40 ` Maciej W. Rozycki [this message]
2016-02-02 22:18 ` Jeffrey Merkey
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=alpine.LFD.2.20.1602021932550.2715@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=Jason@zx2c4.com \
--cc=aconole@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jeffmerkey@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.iooss_linux@m4x.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=tj@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