#124 - handling interrupt - PARI/GP Bug report logs

PARI/GP Bug report logs - #124
handling interrupt

Date: Fri, 10 Dec 2004 17:18:09 UTC

Severity: normal

Done: Bill Allombert <allomber@math.u-bordeaux.fr>

Bug is archived. No further changes may be made.

Message #70 received at 124@pari.math.u-bordeaux.fr (full text, mbox, reply):

Received: (at 124) by pari.math.u-bordeaux.fr; 21 Mar 2006 21:32:42 +0000
From igor@txc.com Tue Mar 21 22:32:42 2006
Received: from transfire.transwitch.com ([63.119.242.254] helo=mailproxy2.txc.com)
	by pari with esmtp (Exim 3.35 #1 (Debian))
	id 1FLoT4-0001iX-00
	for <124@pari.math.u-bordeaux.fr>; Tue, 21 Mar 2006 22:32:42 +0100
Received: from [192.168.10.43] (helo=igor.btc.txc.com)
	by mailproxy2.txc.com with esmtp (Exim 4.42)
	id 1FLoSW-0000cu-4m; Tue, 21 Mar 2006 16:32:08 -0500
Received: from igor.btc.txc.com (localhost.localdomain [127.0.0.1])
	by igor.btc.txc.com (Postfix) with ESMTP id F2D05798093;
	Tue, 21 Mar 2006 16:32:07 -0500 (EST)
Received: (from igor@localhost)
	by igor.btc.txc.com (8.13.4/8.13.4/Submit) id k2LLW7lb018344;
	Tue, 21 Mar 2006 16:32:07 -0500
Date: Tue, 21 Mar 2006 16:32:07 -0500
From: Igor Schein <igor@txc.com>
To: Bill Allombert <allomber@math.u-bordeaux.fr>
Cc: 124@pari.math.u-bordeaux.fr
Subject: Re: Bug#124: handling interrupt
Message-ID: <20060321213207.GK19808@txc.com>
Reply-To: igor@txc.com
References: <20041209215919.GV13401@txc.com> <20041210170624.GB13401@txc.com> <20041210175231.GC30613@seventeen> <20041214201724.GM13401@txc.com> <20050904145150.GV10361@seventeen> <20060318104343.GA8696@txc.com> <20060318112031.GC11349@seventeen>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060318112031.GC11349@seventeen>
User-Agent: Mutt/1.4.2.1i
X-TXC-MailScanner-Information: Please contact SysAdmin group (help@txc.com) for more information
X-TXC-MailScanner: Found to be clean
X-MailScanner-From: igor@txc.com

On Sat, Mar 18, 2006 at 12:20:31PM +0100, Bill Allombert wrote: > On Sat, Mar 18, 2006 at 05:43:43AM -0500, Igor Schein wrote: > > I think I've finally tackled this problem. The dirty solution was: > > > > chmod 0 /lib*/tls > > > > Now the background. First of all, I noticed these problems only occur > > on CentOS 3 machines (both 32 and 64bit). Then I noticed gp gets > > runtime linking to /lib/tls/libc.so.6, which comes from here: > > > > % ldconfig -p | grep libc.so > > libc.so.6 (libc6, hwcap: 0x8000000000000000, OS ABI: Linux 2.4.20) => /lib/tls/libc.so.6 > > libc.so.6 (libc6, hwcap: 0x8000000000000, OS ABI: Linux 2.4.1) => /lib/i686/libc.so.6 > > libc.so.6 (libc6, OS ABI: Linux 2.2.5) => /lib/libc.so.6 > > > > I couldn't quickly figure out how to change that order, so I just hid > > the offending library from the user. As a result, I can't reproduce Someon on the glibc mailing list suggested setting LD_ASSUME_KERNEL. Given ldconfig output as above, I can setenv LD_ASSUME_KERNEL 2.4.1 and that prevents from linking against TLS libc.so. My other question whether or not it's possible to assure that at link time hasn't been answered. Igor

Bill Allombert <allomber@math.u-bordeaux.fr>. Last modified: Sat Aug 26 16:38:00 2023; Machine Name: pari

PARI/GP Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

PARI/GP Bug report logs - #124 handling interrupt

PARI/GP Bug report logs - #124
handling interrupt