From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jesper Skov <jskov@cygnus.co.uk>
To: Zubin Burjor Sethna <sethnaz@sg.adisys.com.au>
Cc: "'ecos discussion mailing list'" <ecos-discuss@cygnus.com>
Subject: RE: [ECOS] gdb vs. eCos?
Date: Mon, 22 Feb 1999 03:06:00 -0000
Message-id: <14033.4281.41371.552106@lassi.cygnus.co.uk>
In-reply-to: < 6006B52C37ABD211AB0900805FFE9D79169244@saturn.sg.adisys.com.au >
References: <6006B52C37ABD211AB0900805FFE9D79169244@saturn.sg.adisys.com.au> <6006B52C37ABD211AB0900805FFE9D79169244@saturn.sg.adisys.com.au>
X-SW-Source: 1999-02/msg00044.html

>>>>> "Zubin" == Zubin Burjor Sethna <sethnaz@sg.adisys.com.au> writes:

Zubin> 	[Zubin Burjor Sethna] Is it possible to resume normal
Zubin> execution after GDB has stopped at a breakpoint in an interrupt
Zubin> handler, on the actual target (not the simulator)? I've read
Zubin> that you cannot execute the RFI (Return From Interrupt) after
Zubin> breaking in an interrupt handler.

If the breakpoint is set at a place where it doesn't trash any CPU
state, it should be possible. 

If you set the breakpoint in code that is storing/restoring CPU state
it will fail, but if you set a breakpoint "in the middle" of an
interrupt handler it should be OK.

Jesper