I added (display-environment-set! #t) to my gambcext.scm thinking it would automate the tedious task of always typing ,e after changing frames in the debugger.
It does show the environment after frame changes but seems buggy as what gets displayed is different (and not correct) from what I get if I do an explicit ,e.
Is it something I don't understand or a bug?
Guillaume
Afficher les réponses par date
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 4-Jun-07, at 11:42 AM, Guillaume Cartier wrote:
I added (display-environment-set! #t) to my gambcext.scm thinking it would automate the tedious task of always typing ,e after changing frames in the debugger.
It does show the environment after frame changes but seems buggy as what gets displayed is different (and not correct) from what I get if I do an explicit ,e.
Is it something I don't understand or a bug?
Could you give an example? When I try it I get the correct output.
Marc
On Mon, Jun 04, 2007 at 02:19:27PM -0400, Marc Feeley wrote:
On 4-Jun-07, at 11:42 AM, Guillaume Cartier wrote:
I added (display-environment-set! #t) to my gambcext.scm thinking it would automate the tedious task of always typing ,e after changing frames in the debugger.
It does show the environment after frame changes but seems buggy as what gets displayed is different (and not correct) from what I get if I do an explicit ,e.
Is it something I don't understand or a bug?
Could you give an example? When I try it I get the correct output.
I noticed the same problem:
((lambda (a) foo) 1)
*** ERROR IN #<procedure #82>, (console)@31.14 -- Unbound variable: foo 1> ,b 0 #<procedure #82> (console)@31:14 foo 1 (interaction) (console)@31:1 ((lambda (a) foo) 1) 1> ,e a = 1 (current-exception-handler) = primordial-exception-handler (current-input-port) = '#<input-output-port #39 (console)> (current-output-port) = '#<input-output-port #39 (console)> (current-directory) = "/home/trex4/laurieti/code/patterns/" 1> ,1 1 (interaction) (console)@31.1 ((lambda (a) foo) 1) 1\1> ,e (current-exception-handler) = primordial-exception-handler (current-input-port) = '#<input-output-port #39 (console)> (current-output-port) = '#<input-output-port #39 (console)> (current-directory) = "/home/trex4/laurieti/code/patterns/" 1\1> (display-environment-set! #t) 1\1> ,0 0 #<procedure #82> (console)@31.14 foo a = 1 (current-exception-handler) = primordial-exception-handler (current-input-port) = '#<input-output-port #39 (console)> (current-output-port) = '#<input-output-port #39 (console)> (current-directory) = "/home/trex4/laurieti/code/patterns/" 1> ,1 1 (interaction) (console)@31.1 ((lambda (a) foo) 1) a = 1 (current-exception-handler) = primordial-exception-handler (current-input-port) = '#<input-output-port #39 (console)> (current-output-port) = '#<input-output-port #39 (console)> (current-directory) = "/home/trex4/laurieti/code/patterns/" 1\1>
A simple workaround is to change macro-repl-context-initial-cont to macro-repl-context-cont in display-continuation in ##repl-within in lib/_repl.scm (around line 1800).
Etienne Laurin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 4-Jun-07, at 3:15 PM, Etienne Laurin wrote:
A simple workaround is to change macro-repl-context-initial-cont to macro-repl-context-cont in display-continuation in ##repl-within in lib/_repl.scm (around line 1800).
Etienne Laurin
Indeed!
Marc