From: hjl@lucon.org (H.J. Lu)
To: martin@mira.isdn.cs.tu-berlin.de
Cc: jgg@ualberta.ca,
libc-hacker@sourceware.cygnus.com (GNU C Library),
drepper@cygnus.com (Ulrich Drepper),
ian@cygnus.com (Ian Lance Taylor),
binutils@sourceware.cygnus.com
Subject: Re: Serious C++ linking error
Date: Sun, 04 Jul 1999 16:51:00 -0000 [thread overview]
Message-ID: <19990704235138.E65F557B9@ocean.lucon.org> (raw)
I am enclosing a simplified testcase for the bug. It is a very
complicated bug due to the weak symbol handling in glibc and gld. It
doesn't happen on Solaris where weak symbols in DSO are treated as
strong and the dynamic linker treats all weak symbols as strong.
I don't know if there is a reasonable fix from glibc or gld. I tend
to believe the bug is in g++. Basically under glibc, for the same
symbol, g++ has to make it either weak or strong in all cases,
compiler-generated or not. Otherwise, bad things can happen.
--
H.J. Lu (hjl@gnu.org)
--
begin 644 shared.tar.gz
M'XL(`"CL?S<``^U876_:,!3E%?^*.\HFJ$@:FWQ(9-U6T76:MJE5^]"'=9-"
MXH"WX%0AB$[3_OOLA*1`H;330A_J\Y`0V]?WVK['/G@R\A(:D(-:A0#3<"P+
M:@#8L0SY!MPEV7L.`\!VNHYCVT;7$;6&Z9`:6%4&56`Z2;T$H#;Z$=W;3C0+
MPUT$M%M,YNL?QK'N5^0#&X9MFIO7'SMFL?[$$HD"&%L&KH%143Q+>.;KO\>X
M'TT#"J\G:<!B??0&(<93"*@71;'OI10.P7#SPGTDT@1:;?0;`5PGHBB$5N/X
MXK0#HJ('QLW+FRO>Z,"K6_.V*]HF-)TF?+'817_04X]=X9;_7[R?-&01K<+'
M%OYCT^@6_.\2T0`P(=A1_-\%^B>?CSY<'&JGH`T1.CL_%1^2S%@^",RRG_))
M$!+<[4&SE35JHWH8)Q`"XV61"T$,U!_%T#B?<L[X4#1OA@T7]`/Q=N$*U0%8
M"%]%\5MX(386^.9".J(\-SOQ1`8&+H1,=L4IDOL-[D'$!O)\FL0P]AC7?1AX
M"=9C5&^V^OTV:#$TWXDH\K&TH?D=M,NHHR777CKJZ%DO9'TOY!&]Y$Y[TDSW
MEZTT'[3P[&-_R3RS()LMEMO.-@QUMC+6)/C%O3'S[\2K'5^^/_IT-^S9AM'/
M5H;_^(X?.R'SGG++!TY,:5/&WX-,JY16^0Y66*]9!3^B'N^A>C(6U66RPKZ<
MBWTQ`4]-P2=%L?_G25&-CVWZSR2XU'\V-J7^L[M*_^T$>RP,:`@9Q_:N$V\X
M]F!&O9\+`G"M'MRCT62U1I;R@(5SL2C9+<2B.__*I6.N))%,MUQ((A$!&"@[
M%UH+`E$>#WD';223Q!O$29IUD+M>$*#TAOJ=;%N[1X(6[J$,JPBVE*?&,Q2E
M!?_U83!@G*55^-C&?\"VX'_7PL0B#L92_PD%J/B_"PP2279!#I1,^7-+?H62
M_YD2J\C'-OX3Q[Z]_S&S^Q_3-A7_=X%U]S\/T03_*@KD?Z+5"Z3\_!85Z@9)
;04%!04%!04%!04%!04%!X;_C+^),&@L`*```
`
end
reply other threads:[~1999-07-04 16:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19990704235138.E65F557B9@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sourceware.cygnus.com \
--cc=drepper@cygnus.com \
--cc=ian@cygnus.com \
--cc=jgg@ualberta.ca \
--cc=libc-hacker@sourceware.cygnus.com \
--cc=martin@mira.isdn.cs.tu-berlin.de \
/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).