From: Daniel Jacobowitz <drow@mvista.com>
To: Daniel Wagner <wagi@gmx.ch>
Cc: gdb@sources.redhat.com
Subject: Re: gdb remote serial protocol
Date: Wed, 28 Aug 2002 06:47:00 -0000 [thread overview]
Message-ID: <20020828134823.GA17605@nevyn.them.org> (raw)
In-Reply-To: <878z2rdrss.fsf@gmx.ch>
On Wed, Aug 28, 2002 at 03:41:23PM +0200, Daniel Wagner wrote:
> [I'm not on the list, please CC me]
>
> Hi
>
> I have some problems with a recent gdb debugging oskit kernels over a
> serial line. Older gdb like 5.0 run flawlessly.
>
> First, there is a new command 'e' which is not documented (Roland
> McGrath told me that). It would be good to have this command
> documented. Thanks.
The step-over-range command ('e') is disabled again in current GDB. It
had some design problem, I think.
> Now to the real problem. Here is small gdb session for demonstration:
This is a consequence of adding %orig_eax :( You have two choices at
the moment: make the stub ignore writes to register 0x29, or build GDB
configured for i386-elf.
Long term we should probably consider the register optional but it's
not clear how close we are to that.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-08-28 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 6:39 Daniel Wagner
2002-08-28 6:47 ` Daniel Jacobowitz [this message]
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=20020828134823.GA17605@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=wagi@gmx.ch \
/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