From: Daniel Jacobowitz <drow@mvista.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: gdb@sources.redhat.com, Zack Weinberg <zack@codesourcery.com>
Subject: Re: Suggestion: Detect inconsistent structure definitions
Date: Wed, 13 Mar 2002 16:02:00 -0000 [thread overview]
Message-ID: <20020313190210.A26841@nevyn.them.org> (raw)
In-Reply-To: <106b01c1cabe$a8e520f0$b6010c0a@catdog>
On Wed, Mar 13, 2002 at 01:41:16PM -0500, Kris Warkentin wrote:
> Seems to me that the linker should be able to detect this problem as
> well....It uses the debug information for error reporting. The problem here
No, the linker uses symbol information. It does -not- read debug info.
> is not so much the definitions of the structures but the reference to a
> variable defined in another object which has a different definition.
That's just a specific case of the problem Zack is describing, really.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-03-14 0:02 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 [this message]
2002-03-14 5:14 ` Kris Warkentin
2002-03-13 16:07 ` Daniel Jacobowitz
2002-03-14 11:13 ` Zack Weinberg
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=20020313190210.A26841@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.com \
--cc=zack@codesourcery.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