From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: avoid creating inter-objfile type pointers
Date: Thu, 04 Nov 2004 15:16:00 -0000 [thread overview]
Message-ID: <20041104151617.GA28125@nevyn.them.org> (raw)
In-Reply-To: <vt27jp2ccks.fsf@zenia.home>
On Thu, Nov 04, 2004 at 02:12:19AM -0500, Jim Blandy wrote:
>
> This fixes a bug that causes incorrect output and crashes, and which
> is not caught by the current test suite. A test could be easily added
> to shlib-call.exp to catch this; I'll try to give that a shot in a
> bit.
>
> 2004-11-04 Jim Blandy <jimb@redhat.com>
>
> * gdbtypes.c (make_qualified_type): Doc fix. Add assertion to
> prevent cross-objfile references.
> (make_cv_type): Doc fix. Don't create cross-objfile references,
> even for stub types.
> (replace_type): Add assertion to prevent cross-objfile references.
> (check_typedef): Never resolve a stub type by copying over a type
> from another file.
Oopsie. This looks sane to me.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-11-04 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 7:13 Jim Blandy
2004-11-04 15:16 ` Daniel Jacobowitz [this message]
2004-11-04 18:32 ` Jim Blandy
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=20041104151617.GA28125@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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