From: Dmitry Gutov <dgutov@yandex.ru>
To: Gemini Lasswell <gazally@runbox.com>
Cc: 22294@debbugs.gnu.org
Subject: bug#22294: 25.0.50; edebug should support jumping into generic methods
Date: Tue, 11 Apr 2017 13:57:39 +0300 [thread overview]
Message-ID: <3c954fc5-fda2-1c30-a251-e2f3fecd8534@yandex.ru> (raw)
In-Reply-To: <m27f476ph9.fsf@runbox.com>
Hi Gemini,
On 03.03.2017 04:52, Gemini Lasswell wrote:
> I've just sent a patch for bug#24753, which fixes an "args out of range"
> error that happened when asking Edebug to step through generic methods,
> after more than one with the same name had been instrumented. With the
> patch in place Edebug is stepping through methods for me. Can you try
> the patch and see if it also fixes the problems you were having?
Thanks for pinging me, but the patch does little to the problem I'm seeing.
Specifically, edebug-step-in doesn't work to step into a function call
that's calling a generic method.
Instead, edebug simply quits and the execution of the current command
continues.
Example:
1. Instrument xref-collect-references.
2. Type M-x xref-find-references.
3. When point reaches the semantic-symref-perform-search call, press 'i'.
next prev parent reply other threads:[~2017-04-11 10:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 18:53 bug#22294: 25.0.50; edebug should support jumping into generic methods Dmitry Gutov
2017-03-03 2:52 ` Gemini Lasswell
2017-04-11 10:57 ` Dmitry Gutov [this message]
2017-04-26 23:12 ` bug#22294: Patch (was: bug#22294: 25.0.50; edebug should support jumping into generic methods) Gemini Lasswell
2017-05-07 2:34 ` bug#22294: Patch Dmitry Gutov
2017-05-07 20:28 ` Gemini Lasswell
2017-05-08 2:19 ` Dmitry Gutov
2017-05-10 5:07 ` bug#22294: Generating Edebug names for generic methods (was: bug#22294: Patch) Gemini Lasswell
2017-05-10 14:18 ` bug#22294: Generating Edebug names for generic methods Dmitry Gutov
2017-05-13 20:58 ` Gemini Lasswell
2017-05-14 1:17 ` Dmitry Gutov
2017-05-14 20:33 ` Dmitry Gutov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c954fc5-fda2-1c30-a251-e2f3fecd8534@yandex.ru \
--to=dgutov@yandex.ru \
--cc=22294@debbugs.gnu.org \
--cc=gazally@runbox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.