From: Nick Garnett <nickg@cygnus.co.uk>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] [i386 PC platform] Problem with external GDB interrupt
Date: Thu, 31 Aug 2000 11:00:00 -0000 [thread overview]
Message-ID: <po8ztdcnxx.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <39AE99CF.B933CB54@redhat.com>
Jonathan Larmour <jlarmour@redhat.com> writes:
> I'm curious as to whether the the x86 increments the PC after *all*
> exceptions, or just "int 3"s. i.e. should we be checking for the breakpoint
> vector, or should we just correct the PC all the time. Anyone know?
INT #3, is defined to be a "trap" exception, which is reported after
the instruction completes, so the PC has already advanced to the next
instruction. The same is also true of hardware and software generated
interrupts.
--
Nick Garnett, eCos Kernel Architect
Red Hat, Cambridge, UK
prev parent reply other threads:[~2000-08-31 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-30 23:56 Fabrice Gautier
2000-08-31 4:30 ` Nick Garnett
2000-08-31 10:45 ` Jonathan Larmour
2000-08-31 11:00 ` Nick Garnett [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=po8ztdcnxx.fsf@balti.cygnus.co.uk \
--to=nickg@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@redhat.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).