Re: Edebug eval problem

[Andreas Schwab]

Hannu Koivisto <azure@iki.fi> writes:

|> Greetings,
|> 
|> I'm debugging a quite large and complex package and I'm seeing the
|> following phenomenon.  Let's say I have code similar to this:
|> 
|> (defvar baz nil)
|> (make-variable-buffer-local 'baz)
|> 
|> (defun foo (bar)
|>   (save-excursion
|>     (cond ((and (stringp baz)
|>                 (string= bar baz))
|>            (message "quux")))))
|> 
|> If I instrument foo for debugging, make my code call it and step
|> the expressions, I note that (stringp baz) evaluates to true
|> and so does (string= bar baz).  So there I am, stopped at the
|> beginning of (message "quux") form, and wondering what were the
|> values of bar and baz.  M-: bar RET gives me a string, M-: baz RET
|> gives me nil.

Type `e' (edebug-eval-expression) to evaluate an expression in the context
of the debugger.

Andreas.

-- 
Andreas Schwab                                  "And now for something
Andreas.Schwab@suse.de                          completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5