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/31502] New: [gdb/testsuite] FAIL: gdb.server/server-connect.exp: tcp6: connect to gdbserver using tcp6:::1 Date: Sat, 16 Mar 2024 15:20:19 +0000 [thread overview] Message-ID: <bug-31502-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31502 Bug ID: 31502 Summary: [gdb/testsuite] FAIL: gdb.server/server-connect.exp: tcp6: connect to gdbserver using tcp6:::1 Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- On aarch64-linux, debian bookworm, I ran into: ... builtin_spawn /home/linux/gdb/build/gdb/testsuite/../../gdb/../gdbserver/gdbserver --once ::1:2417 /home/linux/gdb/build/gdb/testsuite/outputs/gdb.server/server-connect/server-connect^M Can't open socket: Address family not supported by protocol.^M Exiting^M PASS: gdb.server/server-connect.exp: tcp6: start gdbserver target remote tcp6:::1:2417^M A program is being debugged already. Kill it? (y or n) y^M could not connect: Address family not supported by protocol.^M (gdb) FAIL: gdb.server/server-connect.exp: tcp6: connect to gdbserver using tcp6:::1 ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-03-16 15:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-16 15:20 vries at gcc dot gnu.org [this message] 2024-03-18 7:47 ` [Bug testsuite/31502] " vries at gcc dot gnu.org 2024-03-19 7:47 ` vries at gcc dot gnu.org 2024-03-20 18:31 ` cvs-commit at gcc dot gnu.org 2024-03-21 8:03 ` 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-31502-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).