PARI/GP Bug report logs - #124
handling interrupt

Full log

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

Received: (at 124) by pari.math.u-bordeaux.fr; 17 Jan 2005 13:41:47 +0000
From igor@txc.com Mon Jan 17 14:41:47 2005
Received: from transfire.txc.com ([208.5.237.254] helo=mailproxy2.txc.com)
	by pari with esmtp (Exim 3.35 #1 (Debian))
	id 1CqX8d-0006Fb-00
	for <124@pari.math.u-bordeaux.fr>; Mon, 17 Jan 2005 14:41:47 +0100
Received: from [192.168.10.43] (helo=sawara.btc.txc.com)
	by mailproxy2.txc.com with esmtp (Exim 4.42)
	id 1CqX81-0004kl-K0; Mon, 17 Jan 2005 08:41:09 -0500
Received: by sawara.btc.txc.com (Postfix, from userid 7003)
	id 9FD4136C048; Mon, 17 Jan 2005 08:41:07 -0500 (EST)
Date: Mon, 17 Jan 2005 08:41: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: <20050117134107.GM17755@txc.com>
Reply-To: igor@txc.com
References: <20041209215919.GV13401@txc.com> <20041210170624.GB13401@txc.com> <20041210175231.GC30613@seventeen>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041210175231.GC30613@seventeen>
User-Agent: Mutt/1.4.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 Fri, Dec 10, 2004 at 06:52:31PM +0100, Bill Allombert wrote:
> On Fri, Dec 10, 2004 at 12:06:24PM -0500, Igor Schein wrote:
> > Package: pari
> > Version: 2.2.9 (development CHANGES-1.1080)
> > 
> > This is a major recurring problem for me.  In an interactive session
> > running on Opteron machine, ^C stops working, meaning the session is
> > lost.  I can tell it the command ( usually a loop ) does get
> > terminated because the process is in S state, but I never get a prompt
> > back.  I never saw this on a 32bit machine.  Here's a stack trace:
> 
> I already saw that problem while running 32bit GP under screen. I
> assumed it was screen fault, perhaps wrongly.
> 
> > #21 0x00000000005e4add in pop_stack (pts=0x2) at ../src/language/init.c:98
>                                        ^^^^^^^
> I don't know what trust we can have in this value, but if it is really
> 0x2, then something is seriously wrong.
>                                        
> > #22 0x00000000005e689a in pari_err (numerr=19) at ../src/language/init.c:989
> > #23 <signal handler called>
> 
> If you have some idea how to reproduce it, you can try them under
> valgrind (on a x86). Maybe valgrind will catch a problem that do not
> upset the 32bit libc.

Here's a question - is the following issue related to this one?

http://pari.math.u-bordeaux.fr/archives/pari-dev-0403/msg00004.html

That can definitely be reproduced at will.

Thanks

Igor

Send a report that this bug log contains spam.