|
From: | Dmitry Gutov |
Subject: | bug#14443: 24.3.50; log-view-diff and log-view-diff-changeset broken in vc-bzr-change-log-mode and vc-annotate-mode (on w32) |
Date: | Fri, 24 May 2013 00:25:39 +0400 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 |
On 24.05.2013 0:17, Eli Zaretskii wrote:
You could put a breakpoint on call-process and examine its arguments, for example.I've rummaged around the manual a bit, and still don't understand what the recommended workflow is. Should I normally do `edebug-defun' before adding a breakpoint?Actually, I meant GDB on the C level, but since you asked...
Oh. Though I believe it's called something like `Fcall_process' there.
How do I display the value of a local variable?C-x C-e with point after it, I guess. I'm quite sure it worked for me when I used that last.
Then I guess you've used it in a buffer without lexical-binding.
How do I un-instrument a function? AFAICS, there are no commands like `edebug-cancel-', `-reset-' or `-remove-'.Reload the .el file.
Thanks! It's kind of an obvious solution, but I could've spent quite a while looking for a specialized command.
[Prev in Thread] | Current Thread | [Next in Thread] |