From: Ian Lance Taylor <ian@wasabisystems.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Fergal Daly <fergal@esatclear.ie>,
binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] prevent core dump for multiple def symbols
Date: Fri, 11 Jun 2004 15:39:00 -0000 [thread overview]
Message-ID: <m3oenqrtmw.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20040611145341.GA24143@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> writes:
> It seems obvious and correct to me. Is multiple_definition a recent
> callback or did I just miss it when I wrote simple.c? [I won't even
> ask how you have a shared library with multiple definitions of a
> dynamic symbol.]
multiple_definition is not a recent callback. It's been there from
the start.
I agree that for it to be called in this scenario is odd.
Ian
next prev parent reply other threads:[~2004-06-11 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 14:45 Fergal Daly
2004-06-11 14:53 ` Daniel Jacobowitz
2004-06-11 15:12 ` Fergal Daly
2004-06-11 15:39 ` Ian Lance Taylor [this message]
2004-06-11 16:05 ` Fergal Daly
2004-12-07 4:40 ` Daniel Jacobowitz
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=m3oenqrtmw.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=binutils@sources.redhat.com \
--cc=drow@false.org \
--cc=fergal@esatclear.ie \
--cc=gdb-patches@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