From: Eli Zaretskii <eliz@gnu.org>
To: James Nguyen <james@jojojames.com>
Cc: 30151@debbugs.gnu.org
Subject: bug#30151: Debugger API
Date: Fri, 19 Jan 2018 12:19:10 +0200 [thread overview]
Message-ID: <83vafytald.fsf@gnu.org> (raw)
In-Reply-To: <1516353947.1372266.1240815736.7C68AE47@webmail.messagingengine.com> (message from James Nguyen on Fri, 19 Jan 2018 01:25:47 -0800)
> From: James Nguyen <james@jojojames.com>
> Cc: 30151@debbugs.gnu.org
> Date: Fri, 19 Jan 2018 01:25:47 -0800
>
> Ideally, it'd be nice to have something simple that asks me:
> 1. Where to draw breakpoints in the buffer.
> 2. What locals exist and displaying them in some kind of 'locals' buffer.
> 3. Maybe an extra window that will display extraneous information (similar to jdibug's stacktrace buffer)
> 4. I'm missing some other common functionalities between debuggers.
>
> I think some/all of ^ is very similar to gdb-many-windows but I've only ever seen that for *just* gdb.
I agree, but as I said, these capabilities need to be supported by the
underlying debuggers. Currently, only gdb-mi.el provides them because
GDB includes a special interface for debugging front-ends, and that
interface provides the functionality required for the features shown
in gdb-many-windows. If other debuggers can support similar
functionalities, gud.el could be extended to do that for them as well.
Perhaps the first step would be to look at what realgud does to
provide these features. But please be aware that if you are going to
read realgud's source with the intent of doing something similar in
Emacs, you are advised to check with realgud's developers whether they
will be willing to sign legal paperwork, in case you end up copying
some of their code.
Thanks.
next prev parent reply other threads:[~2018-01-19 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 4:56 bug#30151: Debugger API James Nguyen
2018-01-18 14:41 ` Eli Zaretskii
2018-01-19 9:25 ` James Nguyen
2018-01-19 10:19 ` Eli Zaretskii [this message]
2018-01-21 19:16 ` James Nguyen
2019-09-28 22:56 ` Stefan Kangas
2019-09-28 23:53 ` james
2019-09-29 0:13 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83vafytald.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30151@debbugs.gnu.org \
--cc=james@jojojames.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).