This is the mail archive of the 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/testsuite/cp] exception.exp: partially refurbish

On Jan 9, 2004, at 1:48 AM, Michael Elizabeth Chastain wrote:

This is a partial redemption of gdb.cp/

This test script is still not ready yet, mostly because I don't know
what the correct behavior of gdb is for "catch catch" and "catch throw".
So it just bails out after "break main; run".

Jim Ingham added HP-like catch/throw support to the MacOS X gdb last summer. Running this new exception.exp against our gdb I got one UNSUPPORTED (we don't have "info catch" do anything useful). The catch/throw tests failed, but only because our a "throw" breakpoint only knows the "throw location", not the "catch location", and similarly a "catch" breakpoint only knows the "catch location". e.g.


Catchpoint 3 (exception caught), throw location ../../../gdb/src/gdb/testsuite/gdb.c++/, catch location unknown, exception type int
0x0000783c 391 {
(gdb) FAIL: gdb.c++/exception.exp: continue to first throw

The only other failure was from the output of "info breakpoints" -- we don't give an address for our catch/throw support. e.g.

info breakpoints
Num Type Disp Enb Address What
1 breakpoint keep y 0x00002258 in main at ../../../gdb/src/gdb/testsuite/gdb.c++/
breakpoint already hit 1 time
2 catch catch keep y exception catch
3 catch throw keep y exception throw
(gdb) FAIL: gdb.c++/exception.exp: info breakpoints


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