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/31231] [gdb, ppc64le] frame.c:2088: internal-error: get_next_frame_sentinel_okay: Assertion `!is_sentinel_frame_id (this_frame->this_id.value)' failed. Date: Thu, 11 Jan 2024 10:44:28 +0000 [thread overview] Message-ID: <bug-31231-4717-3jOyG6oNps@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31231-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31231 --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- Minimal reproducer: ... $ cat gdb.in file /home/vries/gdb/build/gdb/testsuite/outputs/gdb.base/store/store b 110 run set variable l = 4 ... Backtrace at abort: ... (gdb) bt #0 0x00007ffff6eacb68 in __pthread_kill_implementation () from /lib64/glibc-hwcaps/power10/libc.so.6 #1 0x00007ffff6e4f2e0 in raise () from /lib64/glibc-hwcaps/power10/libc.so.6 #2 0x00007ffff6e2a834 in abort () from /lib64/glibc-hwcaps/power10/libc.so.6 #3 0x0000000010df3d20 in dump_core () at /home/vries/gdb/src/gdb/utils.c:198 #4 0x0000000010df4658 in internal_vproblem (problem=0x12a282b0 <internal_error_problem>, file=0x11925710 "/home/vries/gdb/src/gdb/frame.c", line=2088, fmt=0x11925680 "%s: Assertion `%s' failed.", ap=0x7fffffffd318 "0d\222\021") at /home/vries/gdb/src/gdb/utils.c:450 #5 0x0000000010df4798 in internal_verror (file=0x11925710 "/home/vries/gdb/src/gdb/frame.c", line=2088, fmt=0x11925680 "%s: Assertion `%s' failed.", ap=0x7fffffffd318 "0d\222\021") at /home/vries/gdb/src/gdb/utils.c:476 #6 0x0000000011836650 in internal_error_loc (file=0x11925710 "/home/vries/gdb/src/gdb/frame.c", line=2088, fmt=0x11925680 "%s: Assertion `%s' failed.") at /home/vries/gdb/src/gdbsupport/errors.cc:58 #7 0x0000000010618ab8 in get_next_frame_sentinel_okay (this_frame=...) at /home/vries/gdb/src/gdb/frame.c:2088 #8 0x0000000010b1f064 in rs6000_value_to_register (frame=..., regnum=63, type=0x130e8a70, from=0x132d1470 "") at /home/vries/gdb/src/gdb/rs6000-tdep.c:2747 #9 0x000000001015c238 in gdbarch_value_to_register (gdbarch=0x130d9ea0, frame=..., regnum=63, type=0x130e8a70, buf=0x132d1470 "") at /home/vries/gdb/src/gdb/gdbarch.c:2549 #10 0x0000000010e1b1cc in value_assign (toval=0x131c5aa0, fromval=0x132b56c0) at /home/vries/gdb/src/gdb/valops.c:1247 #11 0x00000000101faff0 in expr::assign_operation::evaluate (this=0x132d0340, expect_type=0x0, exp=0x132aad70, noside=EVAL_NORMAL) at /home/vries/gdb/src/gdb/expop.h:1911 #12 0x00000000105aee34 in expression::evaluate (this=0x132aad70, expect_type=0x0, noside=EVAL_NORMAL) at /home/vries/gdb/src/gdb/eval.c:111 #13 0x0000000010955210 in set_command (exp=0x130db57d "l = 4", from_tty=0) at /home/vries/gdb/src/gdb/printcmd.c:1477 #14 0x0000000010324c24 in do_simple_func (args=0x130db57d "l = 4", from_tty=0, c=0x12eea520) at /home/vries/gdb/src/gdb/cli/cli-decode.c:95 #15 0x000000001032bfb8 in cmd_func (cmd=0x12eea520, args=0x130db57d "l = 4", from_tty=0) at /home/vries/gdb/src/gdb/cli/cli-decode.c:2735 #16 0x0000000010d05664 in execute_command (p=0x130db581 "4", from_tty=0) at /home/vries/gdb/src/gdb/top.c:575 #17 0x00000000105c0084 in command_handler (command=0x130db570 "set variable l = 4") at /home/vries/gdb/src/gdb/event-top.c:566 #18 0x0000000010d0496c in read_command_file (stream=0x1308e980) at /home/vries/gdb/src/gdb/top.c:342 #19 0x00000000103436d0 in script_from_file (stream=0x1308e980, file=0x7ffffffff117 "gdb.in") at /home/vries/gdb/src/gdb/cli/cli-script.c:1642 #20 0x0000000010317848 in source_script_from_stream (stream=0x1308e980, file=0x7ffffffff117 "gdb.in", file_to_open=0x7fffffffe280 "gdb.in") at /home/vries/gdb/src/gdb/cli/cli-cmds.c:730 #21 0x0000000010317a18 in source_script_with_search (file=0x7ffffffff117 "gdb.in", from_tty=0, search_path=0) at /home/vries/gdb/src/gdb/cli/cli-cmds.c:775 #22 0x0000000010317ad8 in source_script (file=0x7ffffffff117 "gdb.in", from_tty=0) at /home/vries/gdb/src/gdb/cli/cli-cmds.c:784 #23 0x00000000107f2868 in catch_command_errors (command=0x10317a9c <source_script(char const*, int)>, arg=0x7ffffffff117 "gdb.in", from_tty=0, do_bp_actions=false) at /home/vries/gdb/src/gdb/main.c:514 #24 0x00000000107f2b84 in execute_cmdargs (cmdarg_vec=0x7fffffffe598, file_type=CMDARG_FILE, cmd_type=CMDARG_COMMAND, ret=0x7fffffffe5c8) at /home/vries/gdb/src/gdb/main.c:610 #25 0x00000000107f4870 in captured_main_1 (context=0x7fffffffe840) at /home/vries/gdb/src/gdb/main.c:1311 #26 0x00000000107f4afc in captured_main (data=0x7fffffffe840) at /home/vries/gdb/src/gdb/main.c:1332 #27 0x00000000107f4c08 in gdb_main (args=0x7fffffffe840) at /home/vries/gdb/src/gdb/main.c:1361 #28 0x000000001001c888 in main (argc=7, argv=0x7fffffffecb8) at /home/vries/gdb/src/gdb/gdb.c:39 (gdb) ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-11 10:44 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-11 10:29 [Bug exp/31231] New: " vries at gcc dot gnu.org 2024-01-11 10:44 ` vries at gcc dot gnu.org [this message] 2024-01-11 10:52 ` [Bug exp/31231] " vries at gcc dot gnu.org 2024-01-11 16:35 ` simark at simark dot ca 2024-01-11 16:51 ` simark at simark dot ca 2024-01-11 18:12 ` cvs-commit at gcc dot gnu.org 2024-01-11 18:12 ` simark at simark dot ca
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-31231-4717-3jOyG6oNps@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).