RE: GUD GDB integration

[Juan Rafael García Blanco]

> -----Original Message-----
> From: help-gnu-emacs [mailto:help-gnu-emacs-
> bounces+jrblanco=gmv.com@gnu.org] On Behalf Of Eli Zaretskii
> Sent: Wednesday, May 23, 2018 5:46 PM
> To: help-gnu-emacs@gnu.org
> Subject: Re: GUD GDB integration
>
> > From: Juan Rafael García Blanco <jrblanco@gmv.com>
> > Date: Wed, 23 May 2018 08:23:04 +0000
> >
> > I wanted to know how gud and gdb interact, i.e. by parsing gdb's output or
> using gdb's built-in scripting engine. I have gone through gud.el and I
> understand interaction is accomplished by parsing gdb's output. Could you
> please confirm my understanding?
>
> There are 2 interfaces: the old one in gud.el uses the CLI output with
> annotations, the new one in gdb-mi.el uses the GDB/MI interface.
>
Thank you. I did not know about annotations.

> > 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.

> > The context for this question is that I'm writing a gdb client, not for 
> > emacs,
> that somehow resembles what gud does. So I wanted to know what gud
> does because it is widely used and it is known to work.
>
> You can look in gdb-mi.el to see the code which uses GDB/MI.
Thank you very much. I will look into that implementation. Thanks.

P Please consider the environment before printing this e-mail.

______________________
This message including any attachments may contain confidential 
information, according to our Information Security Management System,
 and intended solely for a specific individual to whom they are addressed.
 Any unauthorised copy, disclosure or distribution of this message
 is strictly forbidden. If you have received this transmission in error,
 please notify the sender immediately and delete it.

______________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
 puede contener informacion clasificada por su emisor como confidencial
 en el marco de su Sistema de Gestion de Seguridad de la 
Informacion siendo para uso exclusivo del destinatario, quedando 
prohibida su divulgacion copia o distribucion a terceros sin la 
autorizacion expresa del remitente. Si Vd. ha recibido este mensaje 
 erroneamente, se ruega lo notifique al remitente y proceda a su borrado. 
Gracias por su colaboracion.

______________________