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: Mon, 19 Aug 2013 15:55:00 -0000	[thread overview]
Message-ID: <83eh9pllp5.fsf@gnu.org> (raw)
In-Reply-To: <"000001ce9ce9$d4669a10$7d33ce30$@muller"@ics-cnrs.unistra.fr>

> From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> Cc: <gdb-patches@sourceware.org>
> Date: Mon, 19 Aug 2013 16:38:53 +0200
> 
> >   . catch exception [NAME]
> 
>   Currently catch exception is an ADA specific catch type...

Aren't C++ exceptions supported as well?

>   It seems that 'catch catch regex ' 
> could be used...

Less user-friendly, but also fine, IMO.

>   But currently all exception are converted into signals inside
> windows-nat.c code...
>   So that implementing your suggestion would basically mean
> that the Windows API exception would not be converted into 
> signals anymore...

Your changes, OTOH, would cause the inferior be stopped twice for the
same reason, AFAIU.  I don't know what is worse.

>   This is a huge change, which should probably not be enabled 
> by default, no?

I agree, but then catchpoints are never set by default, only by user
command.  So I see no usability problem here.

>   But frankly speaking, I fear that I will never be able to
> implement such a feature :(
>   The list of stuff I wrote for windows OS GDB support
> that was never integrated into main-line is already quite huge...

I can hardly believe that it would be much harder than the 3 options
you suggested.

>   I did look a little a the catching code inside break-catch-throw.c 
> but I still didn't even get how the exception number is supposed to
> be passed to the loop that looks through the list of all breakpoints
> to see if there is a match...

Maybe someone of the senior maintainers could help out here?


  parent reply	other threads:[~2013-08-19 15:55 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
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 [this message]
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=83eh9pllp5.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