This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: minimalistic MI catch support
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: gdb-patches at sourceware dot org, Daniel Jacobowitz <drow at false dot org>, Markus Schiltknecht <markus at bluegap dot ch>, Bob Rossi <bob at brasko dot net>
- Date: Fri, 10 Feb 2006 19:33:28 +1300
- Subject: Re: minimalistic MI catch support
- References: <17386.57501.980555.996896@kahikatea.snap.net.nz>
A few further remark about catchpoints:
(gdb) catch catch
Catchpoint 2 (catch)
(gdb) catch throw
Catchpoint 3 (throw)
(gdb) catch fork
Catchpoint 4 (fork)
(gdb) catch exec
Catchpoint 5 (exec)
(gdb) info break
Num Type Disp Enb Address What
2 breakpoint keep y 0x07dae1aa exception catch
3 breakpoint keep y 0x07daf001 exception throw
4 catch fork keep y
5 catch exec keep y
The first two are of type breakpoint and their nature is given under the
heading "What".
The second two have their own type: "catch fork" and "catch exec" (I must
admit that I don't understand how this gives differerent behaviour from using
"break fork" and "break exec"). Also for some reason, they have no address.
This inconsistent description probably doesn't matter for CLI, but it is
also used for MI output, for which it does seem inappropriate.
Would it be a good idea to change it to:
Num Type Disp Enb Address What
2 breakpoint keep y 0x07dae1aa exception catch
3 breakpoint keep y 0x07daf001 exception throw
4 breakpoint keep y fork
5 breakpoint keep y exec
or something like:
Num Type Disp Enb Address What
2 exception catch keep y 0x07dae1aa
3 exception throw keep y 0x07daf001
4 catch fork keep y
5 catch exec keep y
to make it easier to parse the MI output.
Nick