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/31577] New: [gdb] terminate called after throwing an instance of 'gdb_exception_error'
Date: Fri, 29 Mar 2024 09:34:29 +0000	[thread overview]
Message-ID: <bug-31577-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31577

            Bug ID: 31577
           Summary: [gdb] terminate called after throwing an instance of
                    'gdb_exception_error'
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I ran test-case gdb.server/connect-with-no-symbol-file.exp in an opensuse leap
15.5 container on an fedora asahi aarch64-linux system.

I ran into:
...
(gdb) detach^M
Detaching from program:
target:/data/vries/gdb/build/gdb/testsuite/outputs/gdb.server/connect-with-no-symbol-file/connect-with-no-symbol-file,
process 185104^M
Ending remote debugging.^M
terminate called after throwing an instance of 'gdb_exception_error'^M
^M
^M
Fatal signal: Aborted^M
----- Backtrace -----^M
0x5b6603 gdb_internal_backtrace_1^M
        /data/vries/gdb/src/gdb/bt-utils.c:121^M
0x5b66c3 _Z22gdb_internal_backtracev^M
        /data/vries/gdb/src/gdb/bt-utils.c:167^M
0x7a85d3 handle_fatal_signal^M
        /data/vries/gdb/src/gdb/event-top.c:903^M
0xffff75aa87ff ???^M
0xffff74b977b4 ???^M
0xffff74b98c17 ???^M
0xffff74ea26f3 ???^M
0xffff74ea011b ???^M
0xffff74ea017f ???^M
0xffff74ea0463 ???^M
0x154886f throw_it^M
        /data/vries/gdb/src/gdbsupport/common-exceptions.cc:203^M
0x154891f _Z12throw_verror6errorsPKcSt9__va_list^M
        /data/vries/gdb/src/gdbsupport/common-exceptions.cc:211^M
0x15489ff _Z11throw_error6errorsPKcz^M
        /data/vries/gdb/src/gdbsupport/common-exceptions.cc:226^M
0xac8f2b _ZN13remote_target8readcharEi^M
        /data/vries/gdb/src/gdb/remote.c:9856^M
0xac9f03
_ZN13remote_target6getpktEPSt6vectorIcN3gdb22default_init_allocatorIcSaIcEEEEbPb^M
        /data/vries/gdb/src/gdb/remote.c:10326^M
0xacf3cf
_ZN13remote_target26remote_hostio_send_commandEiiP12fileio_errorPPKcPi^M
        /data/vries/gdb/src/gdb/remote.c:12567^M
0xad03bb _ZN13remote_target12fileio_fstatEiP4statP12fileio_error^M
        /data/vries/gdb/src/gdb/remote.c:12979^M
0xc39877 _Z19target_fileio_fstatiP4statP12fileio_error^M
        /data/vries/gdb/src/gdb/target.c:3315^M
0x7eee5b _ZN20target_fileio_stream4statEP3bfdP4stat^M
        /data/vries/gdb/src/gdb/gdb_bfd.c:467^M
0x7f012b operator()^M
        /data/vries/gdb/src/gdb/gdb_bfd.c:955^M
0x7f015b _FUN^M
        /data/vries/gdb/src/gdb/gdb_bfd.c:956^M
0xf9b837 opncls_bstat^M
        /data/vries/gdb/src/bfd/opncls.c:665^M
---------------------^M
A fatal error internal to GDB has been detected, further^M
debugging is not possible.  GDB will now terminate.^M
This is a bug, please report it.  For instructions, see:^M
<https://www.gnu.org/software/gdb/bugs/>.^M
^M
ERROR: GDB process no longer exists
GDB process exited with wait status 185065 exp84 0 0 CHILDKILLED SIGABRT
SIGABRT
UNRESOLVED: gdb.server/connect-with-no-symbol-file.exp: sysroot=target::
action=permission: detach
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2024-03-29  9:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29  9:34 vries at gcc dot gnu.org [this message]
2024-03-29  9:39 ` [Bug gdb/31577] " vries at gcc dot gnu.org
2024-03-29  9:39 ` vries at gcc dot gnu.org
2024-04-19  8:14 ` vries at gcc dot gnu.org
2024-04-19  8:14 ` [Bug remote/31577] " vries at gcc dot gnu.org
2024-04-19  9:11 ` vries at gcc dot gnu.org
2024-04-19 12:04 ` vries at gcc dot gnu.org
2024-04-27 15:48 ` cvs-commit at gcc dot gnu.org
2024-04-27 15:50 ` 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-31577-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: 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).