#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.

X-Loop: allomber@math.u-bordeaux.fr
Subject: Bug#124: handling interrupt
Reply-To: Bill Allombert <allomber@math.u-bordeaux.fr>, 124@pari.math.u-bordeaux.fr
Resent-From: Bill Allombert <allomber@math.u-bordeaux.fr>
Resent-To: bug-submit-list@pari.math.u-bordeaux.fr
Resent-CC: Karim.Belabas@math.u-psud.fr
Resent-Date: Fri, 10 Dec 2004 18:03:06 UTC
Resent-Message-ID: <handler.124.B124.110270115624027@pari.math.u-bordeaux.fr>
Resent-Sender: allomber@math.u-bordeaux.fr
X-PARI/GP-PR-Message: report 124
X-PARI/GP-PR-Package: pari
X-PARI/GP-PR-Keywords: 
Received: via spool by 124-submit@pari.math.u-bordeaux.fr id=B124.110270115624027
          (code B ref 124); Fri, 10 Dec 2004 18:03:06 UTC
Received: (at 124) by pari.math.u-bordeaux.fr; 10 Dec 2004 17:52:36 +0000
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
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.

Bill Allombert <allomber@math.u-bordeaux.fr>. Last modified: Sat Aug 26 16:37:57 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