[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gcl-devel] Re: Bug#437568: debugging maxima

From: Camm Maguire
Subject: [Gcl-devel] Re: Bug#437568: debugging maxima
Date: Thu, 04 Feb 2010 09:43:44 -0500
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)

Greetings!  The source is (not currently) stored in the image.  If you
know of a function at the base of a call tree which you'd like to
investigate, you can do 
:lisp (setq *debugger-hook* nil)
:lisp (si::use-fast-links nil)
:lisp (trace (foo-function :exit (break)))


And then you will have a backtrace at foo-function which you can
examine with :bt and :bl, among other commands.  Tracing all calls is
(currently) impossible and impractical in any case.  You have to know
where to set the break from reading the source.

When gcl 2.7.0 is released, the source will be carried in the image,
and a type of total tracing facility will be available.

Take care,

Timo Juhani Lindfors <address@hidden> writes:

> Camm Maguire <address@hidden> writes:
>> Greetings!  YOu have the full power of maxima and lisp debuggers.
>> :lisp (setq *debugger-hook* nil), then to_lisp();  Return with
>> (to-maxima). 
> Hmm. How would I for example get a trace of what lisp functions are called
> and with what arguments when I execute
> integrate(sin(x), x);
> ?

Camm Maguire                                        address@hidden
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]