This is the mail archive of the
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: Mon, 19 Aug 2013 18:55:18 +0300
- Subject: Re: [RFC] Add new commands to windows native code.
- References: <"001f01ce9413$72450b20$56cf2160$ at muller"@ics-cnrs.unistra.fr> <83d2pnrmbn dot fsf at gnu dot org> <"000001ce9ce9$d4669a10$7d33ce30$ at muller"@ics-cnrs.unistra.fr>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: "Pierre Muller" <firstname.lastname@example.org>
> Cc: <email@example.com>
> 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
> 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?