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 symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds Date: Tue, 18 Jul 2023 14:11:58 +0000 [thread overview] Message-ID: <bug-30650-4717-V1tMBr1RWq@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30650-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30650 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|testsuite |symtab --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- Hmm, doesn't happen with -readnow, this seems to be a symtab issue. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-18 14:11 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-18 11:49 [Bug testsuite/30650] New: " vries at gcc dot gnu.org 2023-07-18 14:11 ` vries at gcc dot gnu.org [this message] 2023-07-18 15:21 ` [Bug symtab/30650] " vries at gcc dot gnu.org 2023-07-18 17:09 ` vries at gcc dot gnu.org 2023-07-19 7:06 ` vries at gcc dot gnu.org 2023-07-19 7:16 ` vries at gcc dot gnu.org 2023-07-19 9:03 ` vries at gcc dot gnu.org 2023-07-19 9:55 ` vries at gcc dot gnu.org 2023-07-19 10:07 ` vries at gcc dot gnu.org 2023-07-19 11:03 ` vries at gcc dot gnu.org 2023-07-19 11:04 ` vries at gcc dot gnu.org 2023-07-19 11:47 ` vries at gcc dot gnu.org 2023-08-06 14:42 ` vries at gcc dot gnu.org 2023-11-29 15:08 ` jamborm 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-30650-4717-V1tMBr1RWq@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).