help understanding debugger

My main question is why, after c-c, bt doesn't show me the
stack past the c-c break - why not all the way down to the load?

  Type :h and hit Enter for context help.

  [1]> (load "foo")

  *** - LOAD: A file with name foo does not exist
  The following restarts are available:
  ABORT          :R1      Abort main loop
  Break 1 [2]> :bt
  <1/168> #<SYSTEM-FUNCTION SHOW-STACK> 3
  <2/161> #<COMPILED-FUNCTION SYSTEM::PRINT-BACKTRACE>
  <3/155> #<COMPILED-FUNCTION SYSTEM::DEBUG-BACKTRACE>
  <4/146> #<SYSTEM-FUNCTION SYSTEM::READ-EVAL-PRINT> 2
  <5/143> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2-3>
  <6/139> #<SYSTEM-FUNCTION SYSTEM::SAME-ENV-AS> 2
  <7/125> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2>
  <8/123> #<SYSTEM-FUNCTION SYSTEM::DRIVER>
  <9/83> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP>
  <10/80> #<SYSTEM-FUNCTION INVOKE-DEBUGGER> 1
  <11/75> #<SYSTEM-FUNCTION SYSTEM::ERROR-OF-TYPE>
  <12/51> #<COMPILED-FUNCTION LOAD>
  [40] EVAL frame for form (LOAD "foo")
  Printed 12 frames
  Break 1 [2]> ^C

  *** - Ctrl-C: User break
  The following restarts are available:
  ABORT          :R1      Abort debug loop
  ABORT          :R2      Abort main loop
  Break 2 [3]> :bt
  <1/259> #<SYSTEM-FUNCTION SHOW-STACK> 3
  <2/252> #<COMPILED-FUNCTION SYSTEM::PRINT-BACKTRACE>
  <3/246> #<COMPILED-FUNCTION SYSTEM::DEBUG-BACKTRACE>
  <4/237> #<SYSTEM-FUNCTION SYSTEM::READ-EVAL-PRINT> 2
  <5/234> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2-3>
  <6/230> #<SYSTEM-FUNCTION SYSTEM::SAME-ENV-AS> 2
  <7/216> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2>
  <8/214> #<SYSTEM-FUNCTION SYSTEM::DRIVER>
  - T
  Printed 8 frames
  Break 2 [3]> where
  - T

A secondary question is what determines what "where" shows.
Usually it shows something more useful than this.
I suspect the answer is related to the main question - if BT
could show something more useful then where would also.
Similarly, up and top - I imagine that if BT showed load as
I think it should, then top would also show it.

  Break 2 [3]> up
  - T
  Break 2 [3]> up
  - T
  Break 2 [3]> top
  - T
  Break 2 [3]> :bt
  <1/259> #<SYSTEM-FUNCTION SHOW-STACK> 3
  <2/252> #<COMPILED-FUNCTION SYSTEM::PRINT-BACKTRACE>
  <3/246> #<COMPILED-FUNCTION SYSTEM::DEBUG-BACKTRACE>
  <4/237> #<SYSTEM-FUNCTION SYSTEM::READ-EVAL-PRINT> 2
  <5/234> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2-3>
  <6/230> #<SYSTEM-FUNCTION SYSTEM::SAME-ENV-AS> 2
  <7/216> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2>
  <8/214> #<SYSTEM-FUNCTION SYSTEM::DRIVER>
  - T
  Printed 8 frames
  Break 2 [3]> 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list