From: belnac <belnac1@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: gdb
Date: Wed, 07 Apr 2010 03:24:16 +0000 [thread overview]
Message-ID: <1270610656.2491.17.camel@abs1> (raw)
In-Reply-To: <83zl1gvtml.fsf@gnu.org>
On Wed, 2010-04-07 at 06:17 +0300, Eli Zaretskii wrote:
> > From: Sean Sieger <sean.sieger@gmail.com>
> > Date: Tue, 06 Apr 2010 18:08:55 -0400
> >
> > In etc/DEBUG, it says, ``It is a good idea to run Emacs under GDB
> > ... *all the time*.''
>
> It is.
I've been following this particular thread with much interest and would
like to take the opportunity to ask the experts why it is a good idea to
run Emacs under GDB?
next prev parent reply other threads:[~2010-04-07 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 22:08 gdb Sean Sieger
2010-04-07 3:17 ` gdb Eli Zaretskii
2010-04-07 3:24 ` belnac [this message]
2010-04-07 5:27 ` gdb Eli Zaretskii
2010-04-07 9:32 ` gdb Sean Sieger
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=1270610656.2491.17.camel@abs1 \
--to=belnac1@googlemail.com \
--cc=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).