From: George Anzinger <george@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
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, 02 Mar 2004 15:28:45 -0800 [thread overview]
Message-ID: <404518AD.40606@mvista.com> (raw)
In-Reply-To: <20040302220233.GG20227@smtp.west.cox.net>
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).
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.
> +
> #define BREAKPOINT() asm(" int $3");
> #define BREAK_INSTR_SIZE 1
>
> diff -u linux-2.6.3/include/asm-i386/kgdb.h linux-2.6.3/include/asm-i386/kgdb.h
> --- linux-2.6.3/include/asm-i386/kgdb.h 2004-02-26 13:14:41.769186750 -0700
> +++ linux-2.6.3/include/asm-i386/kgdb.h 2004-03-02 14:42:03.232624041 -0700
> @@ -43,6 +43,10 @@
> _GS /* 15 */
> };
>
> +#define PC_REGNUM _PC /* Program Counter */
> +#define SP_REGNUM _ESP /* Stack Pointer */
> +#define PTRACE_PC eip /* Program Counter, in ptrace regs. */
> +
> #define BREAKPOINT() asm(" int $3");
> #define BREAK_INSTR_SIZE 1
>
> diff -u linux-2.6.3/kernel/kgdb.c linux-2.6.3/kernel/kgdb.c
> --- linux-2.6.3/kernel/kgdb.c 2004-03-02 14:25:42.590401068 -0700
> +++ linux-2.6.3/kernel/kgdb.c 2004-03-02 14:51:51.535627684 -0700
> @@ -695,12 +695,24 @@
> /* Master processor is completely in the debugger */
> kgdb_post_master_code(linux_regs, exVector, err_code);
>
> + /* If kgdb is connected, then an exception has occured, and
> + * we need to pass something back to GDB. */
> if (kgdb_connected) {
> - /* reply to host that an exception has occurred */
> ptr = remcom_out_buffer;
> *ptr++ = 'T';
> *ptr++ = hexchars[(signo >> 4) % 16];
> *ptr++ = hexchars[signo % 16];
> + *ptr++ = hexchars[(PC_REGNUM >> 4) % 16];
> + *ptr++ = hexchars[PC_REGNUM % 16];
> + *ptr++ = ':';
> + ptr = kgdb_mem2hex((char *)&linux_regs->PTRACE_PC, ptr, 4);
> + *ptr++ = ';';
> + *ptr++ = hexchars[SP_REGNUM >> 4];
> + *ptr++ = hexchars[SP_REGNUM & 0xf];
> + *ptr++ = ':';
> + ptr = kgdb_mem2hex(((char *)linux_regs) + SP_REGNUM * 4, ptr,
> + 4);
> + *ptr++ = ';';
> ptr += strlen(strcpy(ptr, "thread:"));
> int_to_threadref(&thref, shadow_pid(current->pid));
> ptr = pack_threadid(ptr, &thref);
> @@ -728,11 +740,28 @@
> * we clear out our breakpoints now incase
> * GDB is reconnecting. */
> remove_all_break();
> - remcom_out_buffer[0] = 'S';
> - remcom_out_buffer[1] = hexchars[signo >> 4];
> - remcom_out_buffer[2] = hexchars[signo % 16];
> + /* reply to host that an exception has occurred */
> + ptr = remcom_out_buffer;
> + *ptr++ = 'T';
> + *ptr++ = hexchars[(signo >> 4) % 16];
> + *ptr++ = hexchars[signo % 16];
> + *ptr++ = hexchars[(PC_REGNUM >> 4) % 16];
> + *ptr++ = hexchars[PC_REGNUM % 16];
> + *ptr++ = ':';
> + ptr = kgdb_mem2hex((char *)&linux_regs->PTRACE_PC, ptr,
> + 4);
> + *ptr++ = ';';
> + *ptr++ = hexchars[SP_REGNUM >> 4];
> + *ptr++ = hexchars[SP_REGNUM & 0xf];
> + *ptr++ = ':';
> + ptr = kgdb_mem2hex(((char *)linux_regs) + SP_REGNUM * 4,
> + ptr, 4);
> + *ptr++ = ';';
> + ptr += strlen(strcpy(ptr, "thread:"));
> + int_to_threadref(&thref, shadow_pid(current->pid));
> + ptr = pack_threadid(ptr, &thref);
> + *ptr++ = ';';
> break;
> -
> case 'g': /* return the value of the CPU registers */
> thread = kgdb_usethread;
>
>
> Is this too much extra stuff to bother with, since that information can
> be gotten elsewhere?
>
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2004-03-02 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 22:02 [KGDB][RFC] Send a fuller T packet Tom Rini
2004-03-02 23:28 ` George Anzinger [this message]
2004-03-02 23:36 ` [Kgdb-bugreport] " Tom Rini
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=404518AD.40606@mvista.com \
--to=george@mvista.com \
--cc=amit@av.mvista.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=trini@kernel.crashing.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