From: Hollis R Blanchard <hollis+@andrew.cmu.edu>
To: Kevin Puetz <kp11901@cedarnet.org>
Cc: Justin Vallon <vallon@mindspring.com>,
LinuxPPC-Dev List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: dl-load.c (ld.so) bug??
Date: Wed, 23 Jun 1999 10:19:32 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96L.990623101810.1657A-100000@unix47.andrew.cmu.edu> (raw)
In-Reply-To: <199906231258.HAA25989@www.cedarnet.org>
On Wed, 23 Jun 1999, Kevin Puetz wrote:
> Umm... just thought of this - a segfault in __libc_start_main is the symptom
> of an old R4 binary on a glibc2.1 system... did ElectricFence not get
> updated (just a thought)? Then - if both libraries load - it segfaults when
> electricfence initializes _it's_ glibc dynamic link. One could try
> rebuilding the SRPM and see...
>
> Possible? Or am I on crack (don't know much about efence or glibc internals,
> so... probably the latter.)
Doesn't look like it's an R4 problem... I just rebuilt it and it does the same
thing. A different __libc_start_main thing, I guess.
-Hollis
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-06-23 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199906231258.HAA25989@www.cedarnet.org>
1999-06-23 13:17 ` dl-load.c (ld.so) bug?? Geert Uytterhoeven
1999-06-23 14:19 ` Hollis R Blanchard [this message]
1999-06-23 14:32 ` Kevin Puetz
[not found] <Pine.LNX.4.04.9906211749280.27642-100000@narn.local.drgw.n et>
1999-06-23 14:37 ` Franz Sirl
[not found] <Pine.LNX.3.96L.990622003119.5237E-100000@unix47.andrew.cmu.edu>
1999-06-22 4:39 ` Peter Chang
1999-06-21 22:52 Troy Benjegerdes
1999-06-22 0:04 ` Hollis R Blanchard
1999-06-22 1:57 ` Troy Benjegerdes
1999-06-22 2:48 ` Hollis R Blanchard
1999-06-22 3:09 ` Daniel Jacobowitz
1999-06-22 4:36 ` Peter Chang
1999-06-22 13:52 ` Hollis R Blanchard
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=Pine.LNX.3.96L.990623101810.1657A-100000@unix47.andrew.cmu.edu \
--to=hollis+@andrew.cmu.edu \
--cc=kp11901@cedarnet.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=vallon@mindspring.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.