public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ks132 at yandex dot ru" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/29374] Internal-error when printing exception backtrace
Date: Wed, 20 Jul 2022 20:15:38 +0000 [thread overview]
Message-ID: <bug-29374-4717-93RfxpUHJ8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29374-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29374
--- Comment #1 from ks132 <ks132 at yandex dot ru> ---
Also reproduced in master
$ ~/build-gdb/gdb/gdb -batch -ex "catch throw" -ex r -ex bt a.out
Catchpoint 1 (throw)
warning: Cannot parse .gnu_debugdata section; LZMA support was disabled at
compile time
warning: Cannot parse .gnu_debugdata section; LZMA support was disabled at
compile time
warning: Cannot parse .gnu_debugdata section; LZMA support was disabled at
compile time
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Catchpoint 1 (exception thrown), 0x00007ffff7e256d1 in __cxa_throw () from
/lib64/libstdc++.so.6
#0 0x00007ffff7e256d1 in __cxa_throw () from /lib64/libstdc++.so.6
#1 0x0000000000401430 in Handler::find (this=this@entry=0x7fffffffde90,
../../binutils-gdb/gdb/../gdbsupport/array-view.h:217: internal-error: copy:
Assertion `dest.size () == src.size ()' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
0x4b9b62 gdb_internal_backtrace_1
../../binutils-gdb/gdb/bt-utils.c:122
0x4b9b62 _Z22gdb_internal_backtracev
../../binutils-gdb/gdb/bt-utils.c:168
0x7db474 internal_vproblem
../../binutils-gdb/gdb/utils.c:396
0x7db6b8 _Z15internal_verrorPKciS0_P13__va_list_tag
../../binutils-gdb/gdb/utils.c:476
0x8ef221 _Z14internal_errorPKciS0_z
../../binutils-gdb/gdbsupport/errors.cc:55
0x54d2e1 _ZN3gdb4copyIKhhEEvNS_10array_viewIT_EENS2_IT0_EE
../../binutils-gdb/gdb/../gdbsupport/array-view.h:217
0x54d2e1 _ZN3gdb4copyIKhhEEvNS_10array_viewIT_EENS2_IT0_EE
../../binutils-gdb/gdb/../gdbsupport/array-view.h:215
0x54d2e1 _ZN18dwarf_expr_context12fetch_resultEP4typeS1_lb
../../binutils-gdb/gdb/dwarf2/expr.c:1039
0x56398c dwarf2_evaluate_loc_desc_full
../../binutils-gdb/gdb/dwarf2/loc.c:1519
0x56603e
_Z24dwarf2_evaluate_loc_descP4typeP10frame_infoPKhmP18dwarf2_per_cu_dataP18dwarf2_per_objfileb
../../binutils-gdb/gdb/dwarf2/loc.c:1563
0x56603e dwarf_entry_parameter_to_value
../../binutils-gdb/gdb/dwarf2/loc.c:1269
0x56603e value_of_dwarf_reg_entry
../../binutils-gdb/gdb/dwarf2/loc.c:1366
0x56612c value_of_dwarf_block_entry
../../binutils-gdb/gdb/dwarf2/loc.c:1399
0x566217 loclist_read_variable_at_entry
../../binutils-gdb/gdb/dwarf2/loc.c:3920
0x736648
_Z14read_frame_argRK19frame_print_optionsP6symbolP10frame_infoP9frame_argS7_
../../binutils-gdb/gdb/stack.c:560
0x736dee print_frame_args
../../binutils-gdb/gdb/stack.c:888
0x738611 print_frame
../../binutils-gdb/gdb/stack.c:1391
0x738611
_Z16print_frame_infoRK19frame_print_optionsP10frame_infoi10print_whatii
../../binutils-gdb/gdb/stack.c:1117
0x739dcf backtrace_command_1
../../binutils-gdb/gdb/stack.c:2070
0x739dcf backtrace_command
../../binutils-gdb/gdb/stack.c:2189
0x4e9514 _Z8cmd_funcP16cmd_list_elementPKci
../../binutils-gdb/gdb/cli/cli-decode.c:2516
0x795b7a _Z15execute_commandPKci
../../binutils-gdb/gdb/top.c:699
0x667de1 catch_command_errors
../../binutils-gdb/gdb/main.c:513
0x667eaf execute_cmdargs
../../binutils-gdb/gdb/main.c:608
0x669c4c captured_main_1
../../binutils-gdb/gdb/main.c:1298
0x66a73a captured_main
../../binutils-gdb/gdb/main.c:1319
0x66a73a _Z8gdb_mainP18captured_main_args
../../binutils-gdb/gdb/main.c:1344
0x428bf4 main
../../binutils-gdb/gdb/gdb.c:32
---------------------
This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.
Aborted (core dumped)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-20 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 20:31 [Bug backtrace/29374] New: " ks132 at yandex dot ru
2022-07-20 20:15 ` ks132 at yandex dot ru [this message]
2022-07-23 13:53 ` [Bug backtrace/29374] " ks132 at yandex dot ru
2022-07-24 1:55 ` simark at simark dot ca
2022-07-24 4:00 ` simark at simark dot ca
2022-07-28 2:34 ` 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-29374-4717-93RfxpUHJ8@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: link
Be 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).