From: Arun Sharma <arun.sharma@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: wait4 causes segfault in i386 chroot
Date: Fri, 11 Jun 2004 20:13:11 +0000 [thread overview]
Message-ID: <40CA1257.2010606@intel.com> (raw)
In-Reply-To: <20040610051605.GA21936@cse.unsw.EDU.AU>
On 6/10/2004 7:02 PM, Ian Wienand wrote:
> A guess : the only major difference with the optimised libraries is
> they enable __thread which has the effect of putting errno in the TLS
> area (sysdeps/unix/sysv/linux/i386). TLS uses the %gs register to get
> at the thread local data. Now for some reason the gs register gets
> trashed somewhere along the way, say in a signal handler, it's
> possible that you'd get a segfault? Anyone got any other ideas (cc:
> debian-glibc@lists.debian.org in case they do).
>
Sounds like a variant of this problem:
http://lia64.bkbits.net:8080/linux-ia64-2.5/cset@3f9717925gK7Yi_LUHPyFzsyLpHMsA?nav=index.html|src/|src/arch|src/arch/ia64|src/arch/ia64/ia32|related/arch/ia64/ia32/ia32_signal.c
Is it possible for you to make a tarball for this particular glibc available ? It doesn't fail for me with
# rpm -q glibc
glibc-2.3.2-95.3
-Arun
prev parent reply other threads:[~2004-06-11 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 5:16 wait4 causes segfault in i386 chroot Ian Wienand
2004-06-10 19:08 ` Arun Sharma
2004-06-11 2:02 ` Ian Wienand
2004-06-11 20:13 ` Arun Sharma [this message]
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=40CA1257.2010606@intel.com \
--to=arun.sharma@intel.com \
--cc=linux-ia64@vger.kernel.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