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/29805] [gdb/symtab] FAIL: gdb.threads/access-mem-running-thread-exit.exp: all-stop: access mem (write to global_var, inf=2, iter=1) (GDB internal error) Date: Fri, 18 Nov 2022 17:43:17 +0000 [thread overview] Message-ID: <bug-29805-4717-31y2R70E2n@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29805-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29805 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[gdb.symtab] FAIL: |[gdb/symtab] FAIL: |gdb.threads/access-mem-runn |gdb.threads/access-mem-runn |ing-thread-exit.exp: |ing-thread-exit.exp: |all-stop: access mem (write |all-stop: access mem (write |to global_var, inf=2, |to global_var, inf=2, |iter=1) (GDB internal |iter=1) (GDB internal |error) |error) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-18 17:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-18 16:10 [Bug symtab/29805] New: [gdb.symtab] " vries at gcc dot gnu.org 2022-11-18 17:32 ` [Bug symtab/29805] " vries at gcc dot gnu.org 2022-11-18 17:43 ` vries at gcc dot gnu.org 2022-11-18 17:43 ` vries at gcc dot gnu.org [this message] 2022-11-19 6:30 ` [Bug symtab/29805] [gdb/symtab] " vries at gcc dot gnu.org 2022-11-19 10:33 ` vries at gcc dot gnu.org 2022-11-26 13:13 ` cvs-commit at gcc dot gnu.org 2022-11-26 13:14 ` 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-29805-4717-31y2R70E2n@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).