From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: GDB GUD Variable Buffer
Date: Sun, 28 Aug 2016 19:54:28 +0300 [thread overview]
Message-ID: <83y43gbzqz.fsf@gnu.org> (raw)
In-Reply-To: <618416c0-3a8a-1bd9-2496-b864c3df3697@gmail.com> (message from Augusto Fraga Giachero on Sun, 28 Aug 2016 13:35:51 -0300)
> From: Augusto Fraga Giachero <augustofg96@gmail.com>
> Date: Sun, 28 Aug 2016 13:35:51 -0300
>
> Another question, do you know how to automatically execute an elisp
> function right after I close the GUD session? That's because now I need
> to kill a gdb server process each time I exit gdb.
You could put your function on the gdb-stopped-functions list.
next prev parent reply other threads:[~2016-08-28 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 14:54 Referencing variables beginning with an asterisk in docstrings broken? Nathanael Schweers
2016-08-28 1:55 ` Stefan Monnier
2016-08-28 15:18 ` GDB GUD Variable Buffer Augusto Fraga Giachero
2016-08-28 15:53 ` Eli Zaretskii
2016-08-28 16:35 ` Augusto Fraga Giachero
2016-08-28 16:54 ` Eli Zaretskii [this message]
2016-08-28 23:32 ` Referencing variables beginning with an asterisk in docstrings broken? Nathanael Schweers
2016-08-29 0:32 ` Stefan Monnier
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=83y43gbzqz.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.
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).