This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Add new commands to windows native code.
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 09 Aug 2013 17:05:48 +0300
- Subject: Re: [RFC] Add new commands to windows native code.
- References: <"001f01ce9413$72450b20$56cf2160$ at muller"@ics-cnrs.unistra.fr>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> Date: Thu, 8 Aug 2013 10:44:08 +0200
>
> This patch adds three new commands to windows native code:
> these are three Boolean set/show commands :
>
> 1) set print-first-chance-exception on/off
> to also print a "gdb: unknown target exception ..."
> string on each first-chance exception.
>
> 2) set stop-on-first-chance-exception on/off
> to stop code execution each time a first chance exception occurs.
> and
> 3) set stop-on-debug-string-event on/off
> to stop code execution each time a debug string event occurs.
>
> The third command was particularly useful to
> understand and eliminate a msvcrt debug string event generated
> by GDB code (fix to be submitted in a next patch).
I agree that these are useful features, but I would think they are
more appropriate as part of "catch" implementation for Windows. For
starters, treating these as catchpoints will allow to use all the
features of catchpoints: ignore counts, commands, display in "info
breakpoints", etc.
So would you like to rewrite this as subcommands of "catch"? E.g.,
how about
. catch exception [NAME]
will stop when a specified exception (default: any exception) is
detected
. catch debug-string
will stop whenever any debug string event is detected.
In any case, these are user-visible changes, so they will require
updates to the user manual.
Thanks.