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 exp/31671] New: [gdb/exp] Segmentation fault in value_type Date: Tue, 23 Apr 2024 12:35:38 +0000 [thread overview] Message-ID: <bug-31671-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31671 Bug ID: 31671 Summary: [gdb/exp] Segmentation fault in value_type Product: gdb Version: 13.1 Status: NEW Severity: normal Priority: P2 Component: exp Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- With a 13.2 based package, on SLE-11 using gcc 4.3.4, I run into: ... (gdb) FAIL: gdb.objc/basicclass.exp: breakpoint in category method continue Continuing. Breakpoint 5, -[BasicClass(Private) hiddenMethod] (self=0x605170, _cmd=0x601400 <_OBJC_SELECTOR_TABLE+32>) at /usr/src/packages/BUILD/gdb-13.2/gdb/testsuite/gdb.objc/basicclass.m:62 62 return self; (gdb) FAIL: gdb.objc/basicclass.exp: continue until category method print [self printHi] Fatal signal: Segmentation fault ----- Backtrace ----- 0x4fffc2 gdb_internal_backtrace_1 ../../gdb/bt-utils.c:122 0x4fffc2 _Z22gdb_internal_backtracev ../../gdb/bt-utils.c:168 0x6146d7 handle_fatal_signal ../../gdb/event-top.c:971 0x61475f handle_sigsegv ../../gdb/event-top.c:1044 0x151a6dc0f84f ??? 0x8f2860 _Z10value_typePK5value ../../gdb/value.c:1111 0x683270 value_arg_coerce ../../gdb/infcall.c:184 0x683270 _Z27call_function_by_hand_dummyP5valueP4typeN3gdb10array_viewIS0_EEPFvPviES6_ ../../gdb/infcall.c:1112 0x685c5e _Z21call_function_by_handP5valueP4typeN3gdb10array_viewIS0_EE ../../gdb/infcall.c:786 0x60e290 eval_op_objc_msgcall ../../gdb/eval.c:2176 0x60e290 _ZN4expr22objc_msgcall_operation8evaluateEP4typeP10expression6noside ../../gdb/eval.c:2253 0x61288e _ZN10expression8evaluateEP4type6noside ../../gdb/eval.c:101 0x77c8fc process_print_command_args ../../gdb/printcmd.c:1310 0x77d2cd print_command_1 ../../gdb/printcmd.c:1323 0x533125 _Z8cmd_funcP16cmd_list_elementPKci ../../gdb/cli/cli-decode.c:2543 0x8a24a6 _Z15execute_commandPKci ../../gdb/top.c:690 0x615403 _Z15command_handlerPKc ../../gdb/event-top.c:628 0x6163cd _Z20command_line_handlerOSt10unique_ptrIcN3gdb13xfree_deleterIcEEE ../../gdb/event-top.c:864 0x61498b gdb_rl_callback_handler ../../gdb/event-top.c:256 0x92085f rl_callback_read_char ../../../readline/readline/callback.c:290 0x614b9d gdb_rl_callback_read_char_wrapper_noexcept ../../gdb/event-top.c:192 0x614d6f gdb_rl_callback_read_char_wrapper ../../gdb/event-top.c:231 0x6147ff stdin_event_handler ../../gdb/event-top.c:553 0xac559c gdb_wait_for_event ../../gdbsupport/event-loop.cc:694 0xac5d31 _Z16gdb_do_one_eventi ../../gdbsupport/event-loop.cc:264 0x6f26f9 start_event_loop ../../gdb/main.c:411 0x6f26f9 captured_command_loop ../../gdb/main.c:471 0x6f3f04 captured_main ../../gdb/main.c:1330 0x6f3f04 _Z8gdb_mainP18captured_main_args ../../gdb/main.c:1345 0x414c84 main ../../gdb/gdb.c:32 --------------------- A fatal error internal to GDB has been detected, further debugging is not possible. GDB will now terminate. This is a bug, please report it. For instructions, see: <http://bugs.opensuse.org/>. ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-04-23 12:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-23 12:35 vries at gcc dot gnu.org [this message] 2024-04-23 12:41 ` [Bug exp/31671] " vries at gcc dot gnu.org 2024-04-24 17:03 ` ssbssa at sourceware dot org 2024-05-03 15:38 ` ssbssa at sourceware dot org 2024-05-03 19:45 ` tromey at sourceware dot org 2024-05-03 19:49 ` 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-31671-4717@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).