> From:Andy Wingo <[email protected]> > > Thus, if I understand correctly, the closest I can get to getting source > > info for this trivial case would be to change the script to > > > > (symbol->string "HELLO") > > #t > > Yep. > > > Adding a #t so it can't be tail-called. Then I get > > > > In unknown file: > > ?: 2 [load-compiled/vm > "/home/Mike/.cache/guile/ccache/2.0-LE-4-2.0/home/Mike/tmp.scm.go"] > > In /home/Mike/tmp.scm: > > 1: 1 [#<procedure 13fa550 ()>] > > In unknown file: > > ?: 0 [symbol->string "STRING"] > > ERROR: In procedure symbol->string: > > Is this what you want? It seems right to me...
My expectation of debuggers has been formed by my experience with GDB and MSVC, so I'm still trying to work out for myself where I think Guile's debugging could use improving and where the analogy to GDB is faulty. To say something completely incoherent, I feel like the debugger isn't giving me enough information to solve my problems: I feel like it should be easier to know where I am in the source and where I am in the stack. But to improve on the above incoherent statement, I first need to understand what the expected behavior actually is and how to best take advantage of the functionality that exists. Thanks, -Mike
