Hello Neil,
On 01-03, Neil Jerram wrote:
> Holger Blasum <[EMAIL PROTECTED]> writes:
> Perhaps it would make sense for the debugger to show the source
> position automatically on each step? What do you think?
At least gdb, pydb (python) and ocamldebug (ocd) do this. But any
verbosity trade-offs
Holger Blasum <[EMAIL PROTECTED]> writes:
> Hello Neil,
>
> On 01-02 and 02-02, Neil Jerram wrote:
>> Neil Jerram <[EMAIL PROTECTED]> writes:
> ...
>> debug> step
> ...
>> debug> info frame
> (iterate ad nauseam)
>
> Thanks that was I was looking for! Hadn't thought of using
> "info frame" to spi
Hello Neil,
On 01-02 and 02-02, Neil Jerram wrote:
> Neil Jerram <[EMAIL PROTECTED]> writes:
...
> debug> step
...
> debug> info frame
(iterate ad nauseam)
Thanks that was I was looking for! Hadn't thought of using
"info frame" to spit out the source properties (argh even gdb
does this).
FWIW,
Neil Jerram <[EMAIL PROTECTED]> writes:
> It sounds like what you might in fact want is a report of the
> evaluation of each subexpression within mkmatrix. In that case, the
> correct incantation would be something like this:
[complex incantations suppressed]
It occurred to me later that I shou
Holger Blasum <[EMAIL PROTECTED]> writes:
> Hello guile-user,
Hi Holger,
> in the "Guile Debugging Enhancements" tutorial
> (http://download.gna.org/guile-debugging/guile-debugging.html)
> there is encouragement to play with the source trap context
> parameters.
It's not important for the res
Hello guile-user,
in the "Guile Debugging Enhancements" tutorial
(http://download.gna.org/guile-debugging/guile-debugging.html)
there is encouragement to play with the source trap context
parameters.
What I want to look at are the source file names and
line numbers like eg in any gdb stepping
