[PATCH] gdb.ada/catch_ex.exp, gdb.ada/mi_catch_ex.exp and unsupported catchpoints

[Tom Tromey]

>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:

Joel> The problem is that we need to get to the argument of function we are
Joel> breaking on in order to determine which exception has been raised.
Joel> That's where we really need the debug info. I think I even added
Joel> a comment about that in the code...

Pedro> GDB knows the target's function call ABI (for infcalls), and supposedly
Pedro> this function's prototype is cast in stone as part of the ABI too.
Pedro> GDB could just know where to get the arguments from?

Yeah, it could be done.  Right now though the knowledge in GDB is in a
form that is specific to making infcalls, not decoding them.  So, adding
this functionality would be a significant amount of work, and also
non-trivial to test.  I count 51 calls to set_gdbarch_push_dummy_call in
the tree...

Tom