Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Add new commands to windows native code.
Date: Fri, 09 Aug 2013 14:06:00 -0000	[thread overview]
Message-ID: <83d2pnrmbn.fsf@gnu.org> (raw)
In-Reply-To: <"001f01ce9413$72450b20$56cf2160$@muller"@ics-cnrs.unistra.fr>

> 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.


       reply	other threads:[~2013-08-09 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <"001f01ce9413$72450b20$56cf2160$@muller"@ics-cnrs.unistra.fr>
2013-08-09 14:06 ` Eli Zaretskii [this message]
2013-08-09 15:03   ` Pedro Alves
2013-08-19 14:39   ` Pierre Muller
     [not found]   ` <"000001ce9ce9$d4669a10$7d33ce30$@muller"@ics-cnrs.unistra.fr>
2013-08-19 15:55     ` Eli Zaretskii
2013-08-08  8:44 Pierre Muller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83d2pnrmbn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox