From: Nick Garnett <nickg@cygnus.co.uk>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] [i386 PC platform] Problem with external GDB interrupt
Date: Thu, 31 Aug 2000 04:30:00 -0000 [thread overview]
Message-ID: <poitshel02.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <8AE4B526B977D411841F00A0CC334020052C36@cuz-exchange.sdesigns.net>
Fabrice Gautier <Fabrice_Gautier@sdesigns.com> writes:
> Hi,
>
> When I do a external interrupt with gdb the PC is always one byte too far,
> so if i do not set $pc=$pc-1 the prgram crash when restarting.
>
> Does the HAL_STUB_PLATFORM_STUBS_FIXUP macro is suposed to do something to
> do about this ?
>
Yes. I suspect that this macro was added after the PC HAL was done,
and it was not updated.
It probably needs to look something like this:
// We have to rewind the PC in case of a breakpoint.
#define HAL_STUB_PLATFORM_STUBS_FIXUP() \
CYG_MACRO_START \
if (CYGNUM_HAL_VECTOR_BREAKPOINT == __get_trap_number()) \
put_register(PC, get_register(PC) - 1); \
CYG_MACRO_END
Define it in i386_stub.h, since, despite its name, it is architecture
rather than platform specific.
--
Nick Garnett, eCos Kernel Architect
Red Hat, Cambridge, UK
next prev parent reply other threads:[~2000-08-31 4:30 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 [this message]
2000-08-31 10:45 ` Jonathan Larmour
2000-08-31 11:00 ` Nick Garnett
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=poitshel02.fsf@balti.cygnus.co.uk \
--to=nickg@cygnus.co.uk \
--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).