From: Eli Zaretskii <eliz@gnu.org>
To: nljlistbox2@gmail.com (N. Jackson)
Cc: 22984@debbugs.gnu.org
Subject: bug#22984: 25.0.92; Typo in etc/DEBUG
Date: Fri, 11 Mar 2016 17:59:33 +0200 [thread overview]
Message-ID: <838u1pj996.fsf@gnu.org> (raw)
In-Reply-To: <87h9gd3ux3.fsf@gmail.com> (nljlistbox2@gmail.com)
> From: nljlistbox2@gmail.com (N. Jackson)
> Date: Fri, 11 Mar 2016 11:18:16 -0400
>
> In line 75 of etc/DEBUG there is the following text:
>
> you can start GDB by typing "M-x GDB RET"
>
> IIUC, this should say
>
> you can start GDB by typing "M-x gdb RET"
Thanks, fixed.
> Additionally, it might be helpful if this file mentioned the "debugger"
> that pops up when debug-on-error is non-nil.
That's not really what that file is about.
> This "debugger" doesn't seem to be a debugger at all, but just a
> help window with a backtrace in it.
No, it's a debugger. See the node "Debugger" in the ELisp manual, it
is described there.
> Also, can one use `M-x gdb RET' in the same instance of Emacs that one
> wishes to debug?
No, of course not. When you attach GDB to a program, GDB stops its,
so Emacs will stop responding, and you will not be able to continue
debugging.
But you can run a second instance of the same binary, and debug the
first instance from that second instance. Perhaps this is what you
had in mind, and this is just a misunderstanding caused by the vague
meaning of "instance"?
next prev parent reply other threads:[~2016-03-11 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 15:18 bug#22984: 25.0.92; Typo in etc/DEBUG N. Jackson
2016-03-11 15:59 ` Eli Zaretskii [this message]
2016-03-11 18:30 ` N. Jackson
2016-03-11 18:39 ` Eli Zaretskii
2016-03-11 19:06 ` N. Jackson
2016-03-11 19:42 ` Eli Zaretskii
2016-03-11 20:12 ` N. Jackson
2016-03-11 20:27 ` Eli Zaretskii
2016-03-11 21:18 ` N. Jackson
2016-03-12 8:34 ` Eli Zaretskii
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=838u1pj996.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22984@debbugs.gnu.org \
--cc=nljlistbox2@gmail.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 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.