[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Axiom-developer] breakmode handling bug ?
From: |
Vanuxem Gregory |
Subject: |
Re: [Axiom-developer] breakmode handling bug ? |
Date: |
Sat, 20 Jan 2007 18:57:35 +0100 |
Le samedi 20 janvier 2007 à 13:43 +0100, Waldek Hebisch a écrit :
> > Hello,
> >
> > It is possible in Axiom to modify its behavior when an error is
> > encountered via
> >
> > )set break something
> >
> > But if you set it to 'query', Axiom will ask you if you want to return
> > to top level or enter a Lisp break loop. What I find strange is that
> > this not what Axiom has to do. The code is (g-error.boot):
> >
>
> Could you give more detail on what Axiom is doing for you and what
> it to do. For me it works as follows (both the old release and
> newest wh-sandbox):
>
> (1) -> )set break query
> (1) -> 1/0
>
> >> Error detected within library code:
> division by zero
>
> protected-symbol-warn called with (NIL)
>
> You have three options. Enter:
> continue to continue processing,
> top to return to top level, or
> break to enter a LISP break loop.
>
> Please enter your choice now:
> continue
> Processing will continue where it was interrupted.
> (1) ->
You version seems to correctly handle the piece of code I sent. I have
only two choices:
(1) -> 1/0
>> Error detected within library code:
division by zero
You have two options. Enter:
top to return to top level, or
break to enter a LISP break loop.
Please enter your choice now:
top
(1) ->
It's is on the x86_64 arch. I can reproduce this with gold,
build-improvements and an old one (from Debian).
Anyone who has a x86_64 version of GCL/Axiom can test this ?
Thanks,
Greg