Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options

From	"Maciej W. Rozycki" <macro@linux-mips.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options
Date	2016-02-02 20:50 +0100
Message-ID	<qXP7B-7Ux-17@gated-at.bofh.it> (permalink)
References	<qXweC-1Qr-5@gated-at.bofh.it> <qXweC-1Qr-3@gated-at.bofh.it> <qXyzL-3LF-3@gated-at.bofh.it> <qXyzL-3LF-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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

Thread

[PATCH v4 4/4] pr_emerg add WARN_XX() debugger options Jeffrey Merkey <jeffmerkey@gmail.com> - 2016-02-02 00:40 +0100
  Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options Jeffrey Merkey <jeffmerkey@gmail.com> - 2016-02-02 03:10 +0100
    Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options "Maciej W. Rozycki" <macro@linux-mips.org> - 2016-02-02 20:50 +0100
      Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options Jeffrey Merkey <jeffmerkey@gmail.com> - 2016-02-02 23:20 +0100
  Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options Steven Rostedt <rostedt@goodmis.org> - 2016-02-02 03:10 +0100

csiph-web