Ralf Hemmecke wrote:
>
> > The error message alone gives too little information. Backtrace
> > typically gives more information -- sometimes it is possible
> > to identify routine containing error, in other cases it
> > may give good start point for tracing.
>
> Backtrace? How?
)set break break
Run program up to error -- you will be thrown int Lisp debugger.
Then:
backtrace
>
> And how to start tracing? By using ")trace some-func"?
> Now which function to trace is the question.
At Lisp level (which usually works better for Boot functions
than FriCAS trace):
)lisp (trace |devaluate|)
Lisp by default upcases names, so Boot name goes in bars.
Onece done:
)lisp (untrace |devaluate|)
--
Waldek Hebisch
[email protected]
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/fricas-devel?hl=en.
