From: Werner Van Belle <werner.van.belle@vub.ac.be>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Announcing new Prelinking Guide
Date: Sun, 5 Jan 2003 15:30:20 +0100 [thread overview]
Message-ID: <200301051530.23640.werner.van.belle@vub.ac.be> (raw)
In-Reply-To: <1041772850.1422.21.camel@localhost>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 05 January 2003 14:20, Stefan Jones wrote:
> On Sun, 2003-01-05 at 08:01, Caleb Shay wrote:
> > Prelinking /usr/lib/gimp/1.2/plug-ins/sample_colorize
> > Segmentation fault
>
> I am not really all that surprised that is fails on a plugin as plugins
> are loaded on demand, thus prelinking them has little purpose as the
> loader has little chance of making use of the prelink info. Also they
> could have all sorts of strange dependencies on symbols in the parent
> gimp executable.
That doesn't explain why one set of options doesn't crash (-fmv) while the
other set of options (-amv) does. And after all, a program that segfaults has
a bug in it.
Furthermore, I've exactly the same behaviour as Mr. Caleb. If I start prelink
- -anv it crashes after reading libstdc++.so.5.0.2.
- --
Werner,-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+GEF/xiU3uL/NdUYRAoK0AJ4llTkDJpxRdpt9VdlHWLjLQIeFVQCfYfsc
TwRyyNsPgYj6ZYvzDBwdVJI=
=ehfH
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-01-05 14:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 1:27 [gentoo-dev] Announcing new Prelinking Guide John P. Davis
2003-01-03 8:06 ` Terje Kvernes
2003-01-03 8:25 ` Terje Kvernes
2003-01-03 9:22 ` Stefan Jones
2003-01-03 16:52 ` Terje Kvernes
2003-01-03 19:21 ` Terje Kvernes
2003-01-03 20:54 ` Terje Kvernes
2003-01-04 15:55 ` Stefan Jones
2003-01-04 21:36 ` Terje Kvernes
2003-01-04 14:45 ` Stefan Jones
2003-01-04 22:18 ` Terje Kvernes
2003-01-04 23:11 ` Bart Verwilst
2003-01-04 23:24 ` William Kenworthy
2003-01-05 16:19 ` Paul de Vrieze
2003-01-05 0:10 ` Terje Kvernes
2003-01-03 13:57 ` John P. Davis
2003-01-03 17:23 ` Terje Kvernes
2003-01-03 18:47 ` Toby Dickenson
2003-01-03 19:05 ` Terje Kvernes
2003-01-03 16:11 ` Paul de Vrieze
2003-01-05 1:09 ` Caleb Shay
2003-01-05 3:12 ` Terje Kvernes
2003-01-05 3:52 ` Caleb Shay
2003-01-05 4:39 ` Caleb Shay
2003-01-05 5:27 ` Terje Kvernes
2003-01-05 6:23 ` Caleb Shay
2003-01-05 7:13 ` Terje Kvernes
2003-01-05 8:01 ` Caleb Shay
2003-01-05 13:20 ` Stefan Jones
2003-01-05 14:30 ` Werner Van Belle [this message]
2003-01-05 14:41 ` Stefan Jones
2003-01-05 15:10 ` Dewet Diener
2003-01-05 15:17 ` Bart Lauwers
2003-01-05 15:29 ` Stefan Jones
2003-01-05 14:36 ` Dewet Diener
2003-01-05 5:25 ` Terje Kvernes
2003-01-07 4:02 ` Spider
2003-01-07 7:01 ` Viktor Lakics
2003-01-08 18:49 ` Stefan Jones
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=200301051530.23640.werner.van.belle@vub.ac.be \
--to=werner.van.belle@vub.ac.be \
--cc=gentoo-dev@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox