From: Zack Weinberg <zack@codesourcery.com>
To: gdb@sources.redhat.com
Subject: Re: Suggestion: Detect inconsistent structure definitions
Date: Thu, 14 Mar 2002 11:13:00 -0000 [thread overview]
Message-ID: <20020314191337.GF19703@codesourcery.com> (raw)
In-Reply-To: <20020313190708.B26841@nevyn.them.org>
On Wed, Mar 13, 2002 at 07:07:08PM -0500, Daniel Jacobowitz wrote:
>
> ... When do we have enough information to know that two references
> are 'supposed' to be of the same type, rather than an
> implementation-private type? And in stabs, at least, no debug
> information appears to be emitted for 'extern' statements, so we
> don't know if a file referenced the type it had a different
> definition of or not.
I would argue that this situation is rare, and that most programmers
are unlikely to think of incompatible structure definitions as the
cause of a bug. Therefore, how about a warning issued by default when
the object file is read, but with a way to shut it up per-structure in
.gdbinit?
> Please file a GNATS PR so that this idea doesn't get forgotten.
Done, #420.
zw
next prev parent reply other threads:[~2002-03-14 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 10:22 Zack Weinberg
2002-03-13 10:40 ` Kris Warkentin
2002-03-13 16:02 ` Daniel Jacobowitz
2002-03-14 5:14 ` Kris Warkentin
2002-03-13 16:07 ` Daniel Jacobowitz
2002-03-14 11:13 ` Zack Weinberg [this message]
2002-03-14 21:03 ` Daniel Jacobowitz
2002-03-14 22:11 ` Andrew Cagney
[not found] ` <mailpost.1016043761.7328@news-sj1-1>
2002-03-13 18:35 ` cgd
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=20020314191337.GF19703@codesourcery.com \
--to=zack@codesourcery.com \
--cc=gdb@sources.redhat.com \
/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