PARI/GP Bug report logs - #124
handling interrupt

Full log

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

Received: (at 124) by pari.math.u-bordeaux.fr; 10 Dec 2004 17:52:36 +0000
From allomber@math.u-bordeaux.fr Fri Dec 10 18:52:36 2004
Received: from lns-vlq-7-lil-82-254-193-208.adsl.proxad.net
	([82.254.193.208] helo=yellowpig.yi.org ident=mail)
	by pari with esmtp (Exim 3.35 #1 (Debian))
	id 1CcowW-0006FS-00
	for <124@pari.math.u-bordeaux.fr>; Fri, 10 Dec 2004 18:52:36 +0100
Received: from bill by yellowpig.yi.org with local (Exim 3.35 #1 (Debian))
	id 1CcowR-000357-00; Fri, 10 Dec 2004 18:52:31 +0100
Date: Fri, 10 Dec 2004 18:52:31 +0100
To: igor@txc.com, 124@pari.math.u-bordeaux.fr
Subject: Re: Bug#124: handling interrupt
Message-ID: <20041210175231.GC30613@seventeen>
References: <20041209215919.GV13401@txc.com> <20041210170624.GB13401@txc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041210170624.GB13401@txc.com>
User-Agent: Mutt/1.3.28i
From: Bill Allombert <allomber@math.u-bordeaux.fr>

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.

Cheers,
Bill.

Send a report that this bug log contains spam.