public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug win32/8591] gdb for Win32 does not handle Microsoft C++ exceptions properly. Date: Tue, 21 Mar 2023 16:16:29 +0000 [thread overview] Message-ID: <bug-8591-4717-NU5xWIJhc3@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-8591-4717@http.sourceware.org/bugzilla/> 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.
next parent reply other threads:[~2023-03-21 16:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-8591-4717@http.sourceware.org/bugzilla/> 2023-03-21 16:16 ` tromey at sourceware dot org [this message] 2023-03-21 17:50 ` tromey at sourceware dot org
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=bug-8591-4717-NU5xWIJhc3@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).