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)))
integrate(sin(x),x); 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 <timo.lindf...@iki.fi> writes: > Camm Maguire <c...@maguirefamily.org> 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 c...@maguirefamily.org ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
