This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/20977] GDB exception handling is broken on i686-w64-mingw32
- From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 07 Mar 2017 14:52:02 +0000
- Subject: [Bug gdb/20977] GDB exception handling is broken on i686-w64-mingw32
- Auto-submitted: auto-generated
- References: <bug-20977-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20977
--- Comment #6 from Yao Qi <qiyao at gcc dot gnu.org> ---
(In reply to Orgad Shaneh from comment #5)
> It still happens with 7.12.1 when I type an invalid command. Trace:
>
> 1 msvcrt!abort
> 2 uw_init_context_1
> 3 _Unwind_RaiseException
> 4 __cxa_throw
> 5 throw_exception_cxx common-exceptions.c 303
> 6 throw_exception common-exceptions.c 317
> 7 throw_it common-exceptions.c 373
> 8 throw_verror common-exceptions.c 379
> 9 verror utils.c 525
> 10 error errors.c 43
> 11 undef_cmd_error cli-decode.c 1475
> 12 lookup_cmd cli-decode.c 1517
> 13 execute_command top.c 630
> 14 command_handler event-top.c 641
> 15 command_line_handler event-top.c 833
> 16 gdb_rl_callback_handler event-top.c 213
> 17 rl_callback_read_char callback.c 220
> 18 gdb_rl_callback_read_char_wrapper_noexcept event-top.c 175
> 19 gdb_rl_callback_read_char_wrapper event-top.c 192
> 20 stdin_event_handler event-top.c 568
> 21 handle_file_event event-loop.c 733
> 22 gdb_wait_for_event event-loop.c 884
> 23 gdb_do_one_event event-loop.c 347
> 24 gdb_do_one_event common-exceptions.h 225
> 25 start_event_loop event-loop.c 371
> 26 captured_command_loop main.c 324
> 27 catch_errors exceptions.c 236
> 28 captured_main main.c 1149
> 29 gdb_main main.c 1159
> 30 main gdb.c 32
What is your compiler building GDB? So far, we only tested on DW2 and SJLJ
exception implementations. If your compiler is MSVC, Structured Exception
Handling (SEH) is possibly used. As far as I am aware of, we didn't test it
before.
--
You are receiving this mail because:
You are on the CC list for the bug.