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 testsuite/29726] [gdb] FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=: action=delete: connection to GDBserver succeeded Date: Thu, 27 Oct 2022 07:45:48 +0000 [thread overview] Message-ID: <bug-29726-4717-kRPnhA7XUl@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29726-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29726 --- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> --- FTR, this also the only test-case in the testsuite that for me triggers the: ... # of unexpected core files 1 ... that is generated from $exec: ... $ file build/gdb/testsuite/corebuild/gdb/testsuite/core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/connect-w', real uid: 1000, effective uid: 1000, real gid: 100, effective gid: 100, execfn: '/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/connect-with-no-symbol-file/connect-with-no-symbol-file', platform: 'x86_64' ... due to a segfault in the dynamic linker: ... $ gdb ./outputs/gdb.server/connect-with-no-symbol-file/connect-with-no-symbol-file build/gdb/testsuite/core Reading symbols from ./outputs/gdb.server/connect-with-no-symbol-file/connect-with-no-symbol-file... warning: exec file is newer than core file. [New LWP 28741] Core was generated by `/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/connect-w'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00000000f7dd4550 in ?? () (gdb) ... I'm not sure if it's related, but I thought it's worthwhile mentioning. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-27 7:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-27 7:19 [Bug testsuite/29726] New: " vries at gcc dot gnu.org 2022-10-27 7:21 ` [Bug testsuite/29726] " vries at gcc dot gnu.org 2022-10-27 7:45 ` vries at gcc dot gnu.org [this message] 2022-10-27 8:17 ` vries at gcc dot gnu.org 2022-10-27 8:33 ` vries at gcc dot gnu.org 2022-10-27 9:04 ` vries at gcc dot gnu.org 2022-10-27 9:26 ` luis.machado at arm dot com 2022-10-27 14:56 ` [Bug testsuite/29726] [gdb/testsuite] " 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-29726-4717-kRPnhA7XUl@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).