From: Caleb Shay <caleb@webninja.com>
To: Terje Kvernes <terjekv@math.uio.no>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Announcing new Prelinking Guide
Date: 05 Jan 2003 03:01:13 -0500 [thread overview]
Message-ID: <1041753672.21867.9.camel@Chinstrap.homeunix.net> (raw)
In-Reply-To: <wxx4r8om5lf.fsf@nommo.uio.no>
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
> this is weird. okay, so prelink correctly renames the prelink
> mktemp'ed file to the original. then it does a stat, which returns
> properly, _then_ it segfaults. I peeked a quick peek at the source
> code, but I'm too tired to dig up anything overly useful from C. it
> does however look very buggy. :-/
>
> but it does work fine if you do
>
> prelink -v /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2
>
> right?
Actually, this time it didn't (Abort, not segfault), but
prelink -mvf /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2
worked fine.
Hmm, here's a strange little test case:
#prelink -amv
...
Prelinking /usr/lib/gimp/1.2/plug-ins/sample_colorize
Segmentation fault
#prelink -mvf /usr/lib/gimp/1.2/plug-ins/sample_colorize
<completes fine>
#prelink -amv
...
/usr/lib/libcpuaccel.so.0 4114a000-4114b900
Segmentation fault
#prelink -mvf /usr/lib/libcpuaccel.so.0
<completes fine>
#prelink -amv
...
Prelinking /usr/lib/gimp/1.2/plug-ins/sample_colorize
Segmentation fault
and it will just keep alternating between those two.
Note that libcpuaccel.so.0 is the item that comes just before
the gimp stuff when it gets that far.
licpuaccel is from media-libs/libmpeg2, you probably know what the gimp stuff
is from.
Cheers,
Caleb
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-05 7:55 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 [this message]
2003-01-05 13:20 ` Stefan Jones
2003-01-05 14:30 ` Werner Van Belle
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=1041753672.21867.9.camel@Chinstrap.homeunix.net \
--to=caleb@webninja.com \
--cc=gentoo-dev@gentoo.org \
--cc=terjekv@math.uio.no \
/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