public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/22395] ODR violations
Date: Fri, 12 Mar 2021 17:46:45 +0000 [thread overview]
Message-ID: <bug-22395-4717-jLFcVAlYev@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22395-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22395
--- Comment #5 from Pedro Alves <palves at redhat dot com> ---
(In reply to Tom Tromey from comment #3)
> I got bit debugging an ODR problem in gdb today.
> I'd accidentally given a struct a name that was already in use.
> This would be nice to fix.
Note that in C, it's valid to have different definitions of structures in
different translation units. If GDB isn't coping with that, then I'd say it's
a GDB bug.
(Not saying we shouldn't fix the ODR violation, of course.)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-12 17:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-22395-4717@http.sourceware.org/bugzilla/>
2021-01-09 17:18 ` tromey at sourceware dot org
2021-03-11 19:47 ` tromey at sourceware dot org
2021-03-12 17:03 ` cbiesinger at google dot com
2021-03-12 17:46 ` palves at redhat dot com [this message]
2021-03-12 18:29 ` tromey at sourceware dot org
2021-03-12 18:58 ` schwab@linux-m68k.org
2022-03-06 17:10 ` tromey at sourceware dot org
2022-03-06 17:11 ` tromey at sourceware dot org
2022-05-20 15:04 ` tromey at sourceware dot org
2022-06-02 15:30 ` tromey at sourceware dot org
2022-09-09 0:56 ` tromey at sourceware dot org
2022-11-08 11:01 ` ago at gentoo dot org
2022-11-10 22:09 ` tromey at sourceware dot org
2022-11-10 22:12 ` tromey at sourceware dot org
2022-11-11 5:30 ` sam at gentoo dot org
2023-08-14 9:30 ` vries at gcc dot gnu.org
2023-08-14 12:25 ` vries at gcc dot gnu.org
2023-08-14 12:36 ` tromey at sourceware dot org
2023-08-14 15:50 ` vries at gcc dot gnu.org
2023-08-14 16:32 ` cvs-commit at gcc dot gnu.org
2023-08-14 16:32 ` cvs-commit at gcc dot gnu.org
2023-08-14 16:32 ` cvs-commit at gcc dot gnu.org
2023-08-14 20:53 ` cvs-commit at gcc dot gnu.org
2023-08-15 3:28 ` sam at gentoo dot org
2023-08-17 9:39 ` vries at gcc dot gnu.org
2023-08-17 15:10 ` cvs-commit at gcc dot gnu.org
2023-08-22 17:36 ` vries at gcc dot gnu.org
2023-09-11 6:55 ` vries at gcc dot gnu.org
2023-09-11 7:29 ` vries at gcc dot gnu.org
2023-09-11 20:02 ` sam at gentoo dot org
2023-09-27 7:36 ` sam at gentoo dot 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-22395-4717-jLFcVAlYev@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: link
Be 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).