[Bug win32/8591] gdb for Win32 does not handle Microsoft C++ exceptions properly.

[Bug win32/8591] gdb for Win32 does not handle Microsoft C++ exceptions properly.

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=8591

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
I found this:

https://devblogs.microsoft.com/oldnewthing/20100730-00/?p=13273

I wonder if this default case:

    default:
      /* Treat unhandled first chance exceptions specially.  */
      if (current_event.u.Exception.dwFirstChance)
        return HANDLE_EXCEPTION_UNHANDLED;
      debug_printf ("gdb: unknown target exception 0x%08x at %s\n",
        (unsigned) current_event.u.Exception.ExceptionRecord.ExceptionCode,
        host_address_to_string (
          current_event.u.Exception.ExceptionRecord.ExceptionAddress));
      ourstatus->set_stopped (GDB_SIGNAL_UNKNOWN);


should instead report HANDLE_EXCEPTION_UNHANDLED all the time?


I don't have an MS-compiled program to try unfortunately.

One thing I notice is that the current code (no idea about the code
from 20 years ago) does return UNHANDLED for first-chance exceptions.
So maybe this already works properly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug win32/8591] gdb for Win32 does not handle Microsoft C++ exceptions properly.

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=8591

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
I think this was probably fixed by:

https://sourceware.org/git/?p=binutils-gdb.git;a=commit;f=gdb/win32-nat.c;h=02e423b9b296edcf2fc50161c361062727a3263d

though I can't find this on gdb-patches.

-- 
You are receiving this mail because:
You are on the CC list for the bug.