public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Thorsten Kukuk <kukuk@suse.de>,
	Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Two more vDSO issues
Date: Mon, 08 Mar 2004 13:15:00 -0000	[thread overview]
Message-ID: <jellmbqy2t.fsf@sykes.suse.de> (raw)
In-Reply-To: <20040228142151.GA24758@suse.de> (Thorsten Kukuk's message of "Sat, 28 Feb 2004 15:21:51 +0100")

Thorsten Kukuk <kukuk@suse.de> writes:

> On Fri, Feb 27, Jakub Jelinek wrote:
>
>> Hi!
>> 
>> 1) l->ld needs to be relocated as well (I did not catch this up in my
>>    previous testing, because vDSO was mapped both in the new place and
>>    in the old location)
>> 2) if kernel provides just AT_SYSINFO_EHDR but not AT_SYSINFO, ld.so would
>>    segfault.
>
> Even with this patches, glibc always seg.faults if compiled with
> NPTL support on IA64 when calling rpcgen the first time during build.

Note that it only crashes when starting a program by explicitly calling
the dynamic linker, it appears that __thread_self->private is not
correctly set.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2004-03-08 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27 16:22 Jakub Jelinek
2004-02-28 14:22 ` Thorsten Kukuk
2004-03-08 13:15   ` Andreas Schwab [this message]
2004-03-09  0:06     ` Ulrich Drepper
2004-03-09  9:09       ` Andreas Schwab
2004-02-28 17:55 ` Ulrich Drepper
2004-03-08 13:44 ` Andreas Schwab
2004-03-09 10:43   ` Ulrich Drepper

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=jellmbqy2t.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=jakub@redhat.com \
    --cc=kukuk@suse.de \
    --cc=libc-hacker@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).