All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Troy Benjegerdes <hozer@drgw.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: dl-load.c (ld.so) bug??
Date: Wed, 23 Jun 1999 16:37:25 +0200	[thread overview]
Message-ID: <4.2.0.56.19990623163213.042ffa40@mail.lauterbach.com> (raw)
In-Reply-To: <Pine.LNX.4.04.9906211749280.27642-100000@narn.local.drgw.n et>


At 00:52 22.06.99 , Troy Benjegerdes wrote:


>testcase:
>
>#include <stdio.h>
>int main(void){
>         char * ptr;
>         printf("hello world\n");
>         fflush(stdout);
>         ptr = (char *)malloc(100);
>         free(ptr);
>}
>
>
>compile this with:
>gcc test.c -lefence -g -static
>
>On a PPC glibc-2.1 box, this segfaults in dl-load.c:564
>
>On a x86 Red Hat 6.0 system, it works fine (
>[troybenj@mos6 troybenj]$ ./a.out
>
>   Electric Fence 2.0.5 Copyright (C) 1987-1998 Bruce Perens.
>hello world
>[troybenj@mos6 troybenj]$
>
>
>Either dl-load.c has a serious bug, or ElectricFence is broken on PPC.
>I suspect it's the former, and if so, this would explain the weird
>segfaults I've been seeing.
>
>Can someone that knows glibc better please confirm or deny this for me?

This bug is fixed already in cvs-glibc. I've put up mostly untested RPMS 
for a newer glibc under <ftp://dev.linuxppc.org/users/fsirl/R5>.

It might be that the new IP of dev is still not fully propagated, so use 
169.207.1.122 directly in that case.

Franz.


[[ 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.   ]]

       reply	other threads:[~1999-06-23 14:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.04.9906211749280.27642-100000@narn.local.drgw.n et>
1999-06-23 14:37 ` Franz Sirl [this message]
     [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
1999-06-23 14:32   ` Kevin Puetz
     [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=4.2.0.56.19990623163213.042ffa40@mail.lauterbach.com \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=hozer@drgw.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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.