From: "Patrick O'Grady" <patrick@plasticgrape.com>
To: <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] gdb 'next' problem with i386 HAL
Date: Fri, 24 Aug 2001 07:19:00 -0000 [thread overview]
Message-ID: <001101c12ca8$a88f3550$981ba8c0@yikes> (raw)
I may have some clues about gdb's next problem--as I recall, GDB does a
'next' by 1) poking a breakpoint instruction after the current statement,
and 2) sending a continue instruction to the stub. I would guess that step
(1) isn't supported in the current i386 stub: it's likely that the earlier
GDB computed the length of the current instruction, and used a memory write
command to put the breakpoint in there, and that the current version asks
the target to do that work. HTH...
-patrick
next reply other threads:[~2001-08-24 7:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-24 7:19 Patrick O'Grady [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-29 6:42 John Gumb
2001-08-29 6:47 ` Mark Salter
2001-09-05 8:32 ` Jonathan Larmour
2001-09-05 8:44 ` Mark Salter
2001-09-05 8:55 ` Jonathan Larmour
2001-09-05 9:33 ` Mark Salter
2001-09-05 14:16 ` Jonathan Larmour
2001-09-05 14:59 ` Mark Salter
2001-09-05 15:17 ` Jonathan Larmour
2001-08-23 2:54 John Gumb
2001-08-22 12:20 Allan Young
2001-08-15 15:08 John Gumb
2001-08-16 6:44 ` Jonathan Larmour
2001-08-17 0:31 ` Boris V. Guzhov
2001-08-17 6:17 ` Jonathan Larmour
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='001101c12ca8$a88f3550$981ba8c0@yikes' \
--to=patrick@plasticgrape.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).