From: Zubin Burjor Sethna <sethnaz@sg.adisys.com.au>
To: "'ecos discussion mailing list'" <ecos-discuss@cygnus.com>
Subject: RE: [ECOS] gdb vs. eCos?
Date: Sun, 21 Feb 1999 17:55:00 -0000 [thread overview]
Message-ID: <6006B52C37ABD211AB0900805FFE9D79169244@saturn.sg.adisys.com.au> (raw)
> -----Original Message-----
> From: Jesper Skov [SMTP:jskov@cygnus.co.uk]
> Sent: Wednesday, February 17, 1999 6:22 PM
> To: Stan Shebs
> Cc: kerry@cae-plus.com; ecos-discuss@cygnus.com
> Subject: Re: [ECOS] gdb vs. eCos?
>
>
> Also, using a simulator for debugging the interrupt handlers can be a
> great help since it doesn't trash so much state as the gdb stub does
> (that is, debugging in a SIM is truly transparent for the program
> being run -- at least I haven't had any problems).
>
> I've stepped my way through the PowerPC interrupt handler more than
> once using GDB (although I prefer the SIM way -- it's faster).
>
> Jesper
>
>
[Zubin Burjor Sethna] Is it possible to resume normal execution
after GDB has stopped at a breakpoint in an interrupt handler, on the actual
target (not the simulator)? I've read that you cannot execute the RFI
(Return From Interrupt) after breaking in an interrupt handler.
Zubin
next reply other threads:[~1999-02-21 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-21 17:55 Zubin Burjor Sethna [this message]
[not found] ` < 6006B52C37ABD211AB0900805FFE9D79169244@saturn.sg.adisys.com.au >
1999-02-22 3:06 ` Jesper Skov
-- strict thread matches above, loose matches on Subject: below --
1999-02-12 12:38 Kerry S. Kimbrough
[not found] ` < 199902121646.KAA26430@cae-plus.com >
1999-02-16 15:39 ` Stan Shebs
[not found] ` < 199902162112.NAA25765@andros.cygnus.com >
1999-02-17 3:21 ` Jesper Skov
[not found] ` <199902171527.JAA25835@cae-plus.com>
1999-02-17 10:41 ` Jesper Skov
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=6006B52C37ABD211AB0900805FFE9D79169244@saturn.sg.adisys.com.au \
--to=sethnaz@sg.adisys.com.au \
--cc=ecos-discuss@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).