all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: GUD GDB integration
Date: Thu, 24 May 2018 18:16:43 +0300	[thread overview]
Message-ID: <83vabdaxt0.fsf@gnu.org> (raw)
In-Reply-To: <961A8B2D633A304F92BD712DF06B04DFB227EB66@PTMMAILBOX2.gmv.es> (message from Juan Rafael García Blanco on Thu, 24 May 2018 06:05:04 +0000)

> From: Juan Rafael García Blanco <jrblanco@gmv.com>
> Date: Thu, 24 May 2018 06:05:04 +0000
> 
> > > If so, why is this approach better than writing event handlers using gdb's
> > scheme interpreter?
> >
> > Not sure what you mean by that.  How would Emacs invoke the GDB's
> > Guile interface?
> >
> Well, actually, gdb's guile/python interface would invoke Emacs back when
> hitting a breakpoint, exception, ... I think it is a way to handle gdb events
> synchronously, instead of reading and parsing gdb's output; but that would
> require a connection from the guile part back to Emacs.

I don't see how such a "connection" could work.  The available methods
of communications supported by Emacs either assume Emacs is talking to
a subprocess (via a PTY or a pipe), or support simple display-related
operations used by emacsclient.  Anything else will need development
on the Emacs side, and it cannot be done in Lisp, AFAIU.

IOW, there's no way currently to have Guile interpreter in GDB to
"invoke" Emacs, i.e. instruct Emacs to display a buffer or file in
some specific manner that users of debuggers expect.  E.g., how would
you display breakpoint positions on the fringe?



      reply	other threads:[~2018-05-24 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  8:23 GUD GDB integration Juan Rafael García Blanco
2018-05-23 15:46 ` Eli Zaretskii
2018-05-24  6:05   ` Juan Rafael García Blanco
2018-05-24 15:16     ` Eli Zaretskii [this message]

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=83vabdaxt0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.