This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH: Fix MI stack frame output for synthetic frames


On Fri, Nov 08, 2002 at 05:38:38PM -0500, Andrew Cagney wrote:

> It should be possible to test the "<function called from gdb>" case. 
> All the more main-stream architectures now use dummy-frames so any one 
> of them can be used for the test.
> 
> Can you do that?

OK, I'll write up an MI test case for this and re-post the whole
patch a bit later (off to help a user just now :-).  I can also 
test the signal handler frame one a la gdb.base/signals.exp easily
enough.  

For the tests I added to the Apple gdb, I use the following C file
to test various cases (the function bar() I used for verifying
unwindonsignal was working correctly) in MI and CLI mode.

Thanks,

J

Attachment: inf-call-interrupt.c
Description: Text document


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]