From: Tom Rini <trini@kernel.crashing.org>
To: George Anzinger <george@mvista.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
kgdb-bugreport@lists.sourceforge.net, amit@av.mvista.com,
Pavel Machek <pavel@suse.cz>
Subject: Re: [Kgdb-bugreport] [KGDB][RFC] Send a fuller T packet
Date: Tue, 2 Mar 2004 16:36:35 -0700 [thread overview]
Message-ID: <20040302233635.GM20227@smtp.west.cox.net> (raw)
In-Reply-To: <404518AD.40606@mvista.com>
On Tue, Mar 02, 2004 at 03:28:45PM -0800, George Anzinger wrote:
> Tom Rini wrote:
> >Hello. Since a 'T' packet is allowed to send back information on an
> >arbitrary number of registers, and on PPC32 we've always been including
> >information on the stack pointer and program counter, I was wondering
> >what people thought of the following patch:
> >
> >diff -u linux-2.6.3/include/asm-x86_64/kgdb.h
> >linux-2.6.3/include/asm-x86_64/kgdb.h
> >--- linux-2.6.3/include/asm-x86_64/kgdb.h 2004-02-27
> >11:30:37.445782703 -0700
> >+++ linux-2.6.3/include/asm-x86_64/kgdb.h 2004-03-02
> >14:42:47.854532793 -0700
> >@@ -48,6 +48,10 @@
> > /* Number of bytes of registers. */
> > #define NUMREGBYTES (_LASTREG*8)
> >
> >+#define PC_REGNUM _PC /* Program Counter */
> >+#define SP_REGNUM _RSP /* Stack Pointer */
> >+#define PTRACE_PC rip /* Program Counter, in ptrace regs. */
>
> I would really like to keep this stuff out of kgdb.h since it may be
> included by the user to pick up the BREAKPOINT() (which, by the way we
> should standardize as I note that here it has () while not on the current
> x86).
It's BREAKPOINT() everywhere:
$ grep BREAKPOINT include/asm-*/kgdb.h
include/asm-i386/kgdb.h:#define BREAKPOINT() asm(" int $3");
include/asm-ppc/kgdb.h:#define BREAKPOINT() asm(".long 0x7d821008") /* twge r2, r2 */
include/asm-x86_64/kgdb.h:#define BREAKPOINT() asm(" int $3");
> Isn't there a kgdb_local.h which is used only by kdgd and friends? We
> really do want to keep the name space as clean as possible to prevent
> possible conflicts.
The simple answer is you don't call BREAKPOINT() in your code anywhere.
You call breakpoint() or kgdb_schedule_breakpoint().
The split here is different in that <linux/kgdb.h> should be standalone
(it's not, _yet_).
But this is all an aside to my question. :)
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-03-02 23:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 22:02 Tom Rini
2004-03-02 23:28 ` [Kgdb-bugreport] " George Anzinger
2004-03-02 23:36 ` Tom Rini [this message]
2004-03-03 0:22 ` George Anzinger
2004-03-03 5:06 ` Amit S. Kale
2004-03-03 10:52 ` Pavel Machek
2004-03-03 15:08 ` Tom Rini
2004-03-04 0:36 ` George Anzinger
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=20040302233635.GM20227@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=amit@av.mvista.com \
--cc=george@mvista.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®