This is the mail archive of the
mailing list for the Archer project.
Phil Muldoon wrote:
Tom Tromey wrote:
* Exceptions. Look at the existing longjmp stuff, come up with anThese are all widely reported as issues. Though one should note (quite
rightly) that I know nothing about raising exception in C++ other than
as "regular" C++ programmer, and know nothing about how they are
handled in GDB right now. So my first question is why these
limitations exist. And if they are fixable. I'll take a look at
existing gnats pr's next week.
estimate for the new work. Also look at the current state of the
various "catch" commands, maybe look though gnats to see if anything
is known to be broken.
This ungainly gnat's url:
Contains all the C++ bugs. I'll look at them all in time, but another
quick look at a search regarding exceptions (the feature exception does
not have a category, alas) provides existing bugs:
Synopsis: GDB is not able to show parameters of catch block
Synopsis: gdb for Win32 does not handle Microsoft C++ exceptions
Synopsis: can't step through java exceptions
Synopsis: catch_exceptions() should update gdb stdout et.al.
So there must be more than this, or all our C++ programmer must be
suffering in silence regarding exceptions. I'm guessing I need to be a
better gnat searcher, or define a problem statement around existing
exception support. Beyond the limitations expressed in the previous
mail, are there known proven bugs? longjmp support?