On Sat, Nov 11, 2023 at 08:35:19PM +0800, Qian Yun wrote:
> When I was testing FriCAS built with GCL today, I found a very
> strange error:
>
> The test suite shows one error in bugs2017.output:
>
> fatal tests were:
>
> 1: EQUL: (latex(1), "1")
>
> (This error is probably exposed by recent commit b8b1bd4f,
> "Remove non-default implementations of 'latex'".)
Well, IME unrelated changes can trigger bugs in FriCAS compiled
by GCL.
> This error can be reproduced in FriCAS, but not always --
> you may need to repeat a few times to get the error:
>
> (1) -> latex 1
>
> >> System error:
> Condition in FUNCALL [or a callee]: INTERNAL-SIMPLE-ERROR: Caught fatal
> error [memory may be damaged]
>
> With ")lisp (si::use-fast-links nil)" I can get following backtrace:
>
> BOOT>>:bt
>
> #0 DO-BREAK-LEVEL
> {debug-level=#<conditions::internal-simple-error.0>,g10928=nil,*restart-conditio...}
> [ihs=38]
> #1 INVOKE-DEBUGGER
> {loc0=#<conditions::internal-simple-error.0>,loc1=(((error .
> #<compiled-function...} [ihs=36]
> #2 TexFormat; {loc0=((|prolog| . #<vector 0000000000e2f390>) (|TeX| .
> #<vector 0000000000e2f39...} [ihs=33]
> #3 evalSlotDomain {u=(|TexFormat|),dollar=#<vector
> 0000000000e2e940>,loc2=t,loc3=(#<vector 0000000...} [ihs=32]
> #4 lazyDomainSet {form=(|TexFormat|),thisdomain=#<vector
> 0000000000e2e940>,slot=9} [ihs=31]
> #5 replaceGoGetSlot {env=(#<vector 0000000000e2e940> 5 . |coerce|)}
> [ihs=30]
> #6 SETCAT-;latex;SS;1 {loc0=1,loc1=#<vector 0000000000e2e940>,loc2=(1
> (#<vector 0000000000e2e940> 5 . ...} [ihs=29]
> #7 FUNCALL {loc0=#<compiled-function
> |SETCAT-;latex;SS;1|>,loc1=1,loc2=#<vector 0000000000e...} [ihs=28]
> #8 FUNCALL {loc0=#<compiled-function
> |SETCAT-;latex;SS;1|>,loc1=1,loc2=#<vector 0000000000e...} [ihs=27]
Thanks for info. I can not reproduce this failure. replaceGoGetSlot
should be called only in first invocation, if failure appears on
later invocation call should use cached result of lookup from
domain vector and go directly to appropriate function in
TexFormat. Above it seems that initialization of TexFormat
failed...
OTOH I do not have 100% confidence in GCL backtrace. Debugging
misterious problem in the past, backtrace suggested a failure
point. But debugging printouts indicated that execution
made more progress.
--
Waldek Hebisch
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/ZU%2BO/SOl3gyQR2Ig%40fricas.org.
