From: Peter Chang <weasel@cs.stanford.edu>
To: Hollis R Blanchard <hollis+@andrew.cmu.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: dl-load.c (ld.so) bug??
Date: Mon, 21 Jun 1999 21:39:06 -0700 [thread overview]
Message-ID: <v04205407b394c3a178eb@[209.239.164.131]> (raw)
In-Reply-To: <Pine.LNX.3.96L.990622003119.5237E-100000@unix47.andrew.cmu.edu>
> > Uhhh... both of these are legal.
>
>Yes, exactly. There is no reason they should do anything bad. Now compile them
>with 'gcc -o bug main.c -lefence -g -static'. They both segfault.
Ooops. I thought that you meant that the were illegal and were not
getting caught. Sorry.
\p
---
sed quis custodiet ipsos custodes
--Juvenal *Satire* VI, 165
[[ 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 parent reply other threads:[~1999-06-22 4:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96L.990622003119.5237E-100000@unix47.andrew.cmu.edu>
1999-06-22 4:39 ` Peter Chang [this message]
[not found] <Pine.LNX.4.04.9906211749280.27642-100000@narn.local.drgw.n et>
1999-06-23 14:37 ` dl-load.c (ld.so) bug?? Franz Sirl
[not found] <199906231258.HAA25989@www.cedarnet.org>
1999-06-23 13:17 ` Geert Uytterhoeven
1999-06-23 14:19 ` Hollis R Blanchard
1999-06-23 14:32 ` Kevin Puetz
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='v04205407b394c3a178eb@[209.239.164.131]' \
--to=weasel@cs.stanford.edu \
--cc=hollis+@andrew.cmu.edu \
--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.