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/31197] New: [gdb/testsuite, root] FAIL: gdb.base/gdb-index-err.exp: flag=: try to write index to a non-writable directory Date: Fri, 29 Dec 2023 05:41:59 +0000 [thread overview] Message-ID: <bug-31197-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31197 Bug ID: 31197 Summary: [gdb/testsuite, root] FAIL: gdb.base/gdb-index-err.exp: flag=: try to write index to a non-writable directory 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: --- In a container with openSUSE tumbleweed, I see: ... FAIL: gdb.base/gdb-index-err.exp: flag=: try to write index to a non-writable directory FAIL: gdb.base/gdb-index-err.exp: flag=-dwarf-5: try to write index to a non-writable directory ... I suppose this is because I'm running as root. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-12-29 5:42 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-29 5:41 vries at gcc dot gnu.org [this message] 2023-12-30 19:04 ` [Bug testsuite/31197] " cvs-commit at gcc dot gnu.org 2023-12-30 19:04 ` 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-31197-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).