public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27813] FAIL: gdb.linespec/cpcompletion.exp: incomplete-scope-colon: tab complete "b cpls.cc:'ns_incomplete_scope_colon_test::i" (clearing input line) (timeout) Date: Tue, 13 Sep 2022 06:57:12 +0000 [thread overview] Message-ID: <bug-27813-4717-oGsGqk838O@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27813-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27813 --- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> --- I added this to capture the moment when the SIGINT is caught: ... diff --git a/readline/readline/signals.c b/readline/readline/signals.c index 8fedc370a1a..dffd66ae553 100644 --- a/readline/readline/signals.c +++ b/readline/readline/signals.c @@ -166,6 +166,7 @@ _rl_signal_handler (int sig) static RETSIGTYPE rl_signal_handler (int sig) { + __builtin_abort (); _rl_caught_signal = sig; SIGHANDLER_RETURN; } ... Backtrace of corresponding core file: ... (gdb) bt #0 raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00000000007606b6 in handle_fatal_signal (sig=6) at gdb/event-top.c:971 #2 <signal handler called> #3 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #4 0x00007ffa99911375 in __GI_abort () at abort.c:79 #5 0x0000000000ce4336 in rl_signal_handler (sig=2) at readline/readline/signals.c:169 #6 <signal handler called> #7 0x0000000000ce0f1a in update_line ( old=0x3897050 "(gdb) maintenance selftest name_that_does_not_exist", old_face=0x389f060 '0' <repeats 51 times>, new=0x38a7070 "(gdb) maintenance selftest name_that_does_not_exist", new_face=0x38af080 '0' <repeats 51 times>, current_line=0, omax=32766, nmax=32766, inv_botlin=0) at readline/readline/display.c:1938 #8 0x0000000000cdfd6b in rl_redisplay () at readline/readline/display.c:1518 #9 0x0000000000cc87dd in _rl_internal_char_cleanup () at readline/readline/readline.c:533 #10 0x0000000000cc8b24 in readline_internal_char () at readline/readline/readline.c:681 #11 0x0000000000ce8c63 in rl_callback_read_char () at readline/readline/callback.c:264 #12 0x000000000075f4a0 in gdb_rl_callback_read_char_wrapper_noexcept () at gdb/event-top.c:188 #13 0x000000000075f527 in gdb_rl_callback_read_char_wrapper (client_data=0x3537150) at gdb/event-top.c:205 #14 0x000000000075fc74 in stdin_event_handler (error=0, client_data=0x3537150) at gdb/event-top.c:525 #15 0x00000000013a9b60 in handle_file_event (file_ptr=0x37e4490, ready_mask=1) at gdbsupport/event-loop.cc:574 #16 0x00000000013aa0e8 in gdb_wait_for_event (block=1) at gdbsupport/event-loop.cc:695 #17 0x00000000013a8fbc in gdb_do_one_event (mstimeout=-1) at gdbsupport/event-loop.cc:265 #18 0x00000000008a65b3 in start_event_loop () at gdb/main.c:411 #19 0x00000000008a66d3 in captured_command_loop () at gdb/main.c:471 #20 0x00000000008a7eeb in captured_main (data=0x7ffff205b580) at gdb/main.c:1330 #21 0x00000000008a7f51 in gdb_main (args=0x7ffff205b580) at gdb/main.c:1345 #22 0x000000000041506e in main (argc=9, argv=0x7ffff205b698) at gdb/gdb.c:32 (gdb) ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-13 6:57 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-03 13:28 [Bug gdb/27813] New: " vries at gcc dot gnu.org 2021-05-03 23:21 ` [Bug gdb/27813] " vries at gcc dot gnu.org 2022-04-06 21:05 ` vries at gcc dot gnu.org 2022-04-06 21:17 ` simark at simark dot ca 2022-09-12 9:02 ` luis.machado at arm dot com 2022-09-12 14:45 ` vries at gcc dot gnu.org 2022-09-12 15:02 ` vries at gcc dot gnu.org 2022-09-12 15:48 ` vries at gcc dot gnu.org 2022-09-13 6:57 ` vries at gcc dot gnu.org [this message] 2022-09-13 7:40 ` vries at gcc dot gnu.org 2022-09-13 7:41 ` vries at gcc dot gnu.org 2022-09-13 12:57 ` vries at gcc dot gnu.org 2022-09-16 13:58 ` vries at gcc dot gnu.org 2023-05-24 9:20 ` [Bug cli/27813] " vries at gcc dot gnu.org 2023-05-24 9:41 ` vries at gcc dot gnu.org 2023-05-24 9:42 ` vries at gcc dot gnu.org 2023-05-24 10:42 ` vries at gcc dot gnu.org 2023-06-07 12:57 ` cvs-commit at gcc dot gnu.org 2023-06-14 5:51 ` vries at gcc dot gnu.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-27813-4717-oGsGqk838O@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).