public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "mehmetgelisin at aol dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug fortran/27341] [dwarf-5] FAIL: gdb.fortran/function-calls.exp: p derived_types_and_module_calls::pass_cart_nd(c_nd) Date: Fri, 10 Sep 2021 19:40:49 +0000 [thread overview] Message-ID: <bug-27341-4717-D0CRlGwHMD@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27341-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27341 Mehmet gelisin <mehmetgelisin at aol dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mehmetgelisin at aol dot com --- Comment #15 from Mehmet gelisin <mehmetgelisin at aol dot com> --- minimal version: ... 1 #include <iostream> 2 3 void http://www.iu-bloomington.com/ 4 function1 (int val) 5 { 6 throw val; 7 } 8 9 void 10 function3 (int val) 11 { https://www.webb-dev.co.uk/ 12 { 13 try 14 { 15 function1 (val); 16 } https://waytowhatsnext.com/ 17 catch (...) 18 { 19 std::cout << "Caught and handled function1 exception" << std::endl; 20 } http://www.acpirateradio.co.uk/ 21 } 22 } 23 24 int 25 main (void) http://www.logoarts.co.uk/ 26 { 27 function3 (3); 28 29 return 0; 30 } http://www.slipstone.co.uk/ ... Compiled like: ... http://embermanchester.uk/ $ $ g++ nextoverthrow.cc -g ... Reproduces like so: ... http://connstr.net/ $ gdb -batch ./a.out -ex 'b 27' -ex run -ex next Breakpoint 1 at 0x400ae4: file nextoverthrow.cc, line 27. http://joerg.li/ Breakpoint 1, main () at nextoverthrow.cc:27 27 function3 (3); infrun.c:6384: internal-error: void https://komiya-dental.com/ process_event_stop_test(execution_control_state*): Assertion `ecs->event_thread->control.exception_resume_breakpoint != NULL' failed. ... With -ex "set debug infrun 1", we see: http://www.jopspeech.com/ ... Breakpoint 1, main () at nextoverthrow.cc:27 27 function3 (3); [infrun] infrun_async: enable=0 [infrun] clear_proceed_status_thread: process 4142 [infrun] proceed: addr=0xffffffffffffffff, signal=GDB_SIGNAL_DEFAULT http://www.wearelondonmade.com/ [infrun] start_step_over: step-over queue now empty [infrun] start_step_over: resuming [process 4142] for step-over [infrun] resume_1: step=1, signal=GDB_SIGNAL_0, trap_expected=1, current thread [process 4142] at 0x400ae4 [infrun] infrun_async: enable=1 [infrun] prepare_to_wait: prepare_to_wait [infrun] proceed: [process 4142] resumed http://www.compilatori.com/ [infrun] target_wait (-1.0.0, status) = [infrun] 4142.4142.0 [process 4142], [infrun] status->kind = stopped, signal = GDB_SIGNAL_TRAP [infrun] handle_inferior_event: status->kind = stopped, signal = GDB_SIGNAL_TRAP [infrun] handle_signal_stop: stop_pc=0x400ae9 http://www-look-4.com/ [infrun] process_event_stop_test: stepping inside range [0x400ae4-0x400aee] [infrun] resume_1: step=1, signal=GDB_SIGNAL_0, trap_expected=0, current thread [process 4142] at 0x400ae9 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-10 19:40 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-03 22:39 [Bug fortran/27341] New: " vries at gcc dot gnu.org 2021-02-04 7:53 ` [Bug fortran/27341] " vries at gcc dot gnu.org 2021-02-04 9:48 ` vries at gcc dot gnu.org 2021-02-05 12:32 ` vries at gcc dot gnu.org 2021-02-09 22:28 ` cvs-commit at gcc dot gnu.org 2021-02-09 22:30 ` vries at gcc dot gnu.org 2021-02-09 22:31 ` vries at gcc dot gnu.org 2021-03-07 16:58 ` cvs-commit at gcc dot gnu.org 2021-03-07 16:59 ` vries at gcc dot gnu.org 2021-07-15 1:35 ` sherrixotyv29 at gmail dot com 2021-07-15 5:54 ` vries at gcc dot gnu.org 2021-07-21 4:06 ` ampva300 at gmail dot com 2021-07-21 7:21 ` vries at gcc dot gnu.org 2021-08-09 9:41 ` phillipsaeverett84 at gmail dot com 2021-08-10 11:45 ` ucelsanicin at yahoo dot com 2021-09-02 11:05 ` donipah907 at mtlcz dot com 2021-09-02 11:14 ` mark at klomp dot org 2021-09-06 9:06 ` focixujo at livinginsurance dot co.uk 2021-09-06 9:12 ` focixujo at livinginsurance dot co.uk 2021-09-10 19:40 ` mehmetgelisin at aol dot com [this message] 2021-09-22 16:40 ` mervegunesli at aol dot com 2021-09-26 13:31 ` tes.vik1986 at gmail dot com 2021-10-04 4:39 ` olivernicholle9052 at gmail dot com 2021-10-05 4:33 ` cartwrighthlmv67 at gmail dot com 2021-10-09 11:00 ` gulsenenginar at aol dot com 2021-10-10 3:40 ` cartwrighthlmv67 at gmail dot com 2021-10-10 16:11 ` oficaj3 at gmail dot com 2021-10-11 11:26 ` albertopyhy93 at gmail dot com 2021-10-18 6:45 ` pagefitzpatrick687 at gmail dot com 2021-10-18 19:57 ` ahmedsayeed1982 at hotmail dot com 2021-10-18 19:59 ` ahmedsayeed1982 at hotmail dot com 2021-10-19 7:14 ` progonsaytu at gmail dot com 2021-10-24 10:02 ` glassmtech at ukr dot net 2021-10-25 8:20 ` pagewhitehea034 at gmail dot com 2021-10-25 18:38 ` ahappliancerepair1 at gmail dot com 2021-10-29 10:57 ` kimolsun2020 at outlook dot com 2021-11-02 9:31 ` amosohxx90 at gmail dot com 2021-11-04 9:21 ` bahamianiridescent at gmail dot com 2021-11-05 9:27 ` bertbxi85 at gmail dot com 2021-11-08 11:50 ` richardsboyer67 at gmail dot com 2021-11-09 11:45 ` johnsjvi95 at gmail dot com 2021-11-17 13:02 ` blareblare2000mar at gmail dot com 2022-10-23 18:52 ` newcastlescaffolding at gmail dot com 2023-03-15 0:57 ` sz1922833 at gmail dot com 2023-03-15 0:57 ` sz1922833 at gmail dot com 2023-03-20 9:55 ` qas_07 at icloud dot com
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-27341-4717-D0CRlGwHMD@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).