From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: 13303@debbugs.gnu.org
Subject: bug#13303: 24.2.91; gdb under emacs broken for break commands
Date: Sat, 29 Dec 2012 14:55:56 +0200 [thread overview]
Message-ID: <83han5kof7.fsf@gnu.org> (raw)
In-Reply-To: <851ue9doqc.fsf@stephe-leake.org>
> From: Stephen Leake <stephen_leake@stephe-leake.org>
> Cc: 13303@debbugs.gnu.org
> Date: Sat, 29 Dec 2012 07:31:07 -0500
>
> > Anyway, the annoyance with no "> " prompt on Posix hosts is a known
> > problem with GDB versions older than 7.5; see bug#11279. You can work
> > around it by typing this command at the first GDB prompt:
> >
> > (gdb) set interactive-mode off
> >
> > GDB 7.5 fixed that problem, so upgrading your GDB will remove the need
> > to use the above work-around.
>
> That does restore the "> " prompt, but it also restores EOF behavior (it
> now quits the debugger).
I don't understand: you are supposed to end the breakpoint commands by
typing just "end" at the "> " prompt. It works for me with GDB 7.3
and Emacs 24.2.91 on GNU/Linux; if it doesn't work for you, please
tell what happens when you type "end" to end the breakpoint commands.
So what happens when sending EOF is not really relevant here, IMO.
(That command only works on GNU/Linux at the top level, not during
specification of breakpoint commands.)
> So the core problem remains: there is no way to terminate prompting
> for new command lines, without quiting the debugger.
See above: "end" works for me.
next prev parent reply other threads:[~2012-12-29 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 4:04 bug#13303: 24.2.91; gdb under emacs broken for break commands Stephen Leake
2012-12-29 8:17 ` Eli Zaretskii
2012-12-29 12:31 ` Stephen Leake
2012-12-29 12:55 ` Eli Zaretskii [this message]
2012-12-29 15:28 ` Stephen Leake
2012-12-29 17:19 ` Eli Zaretskii
2012-12-29 18:40 ` Stephen Leake
2012-12-29 18:56 ` Eli Zaretskii
2012-12-29 17:54 ` 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
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=83han5kof7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13303@debbugs.gnu.org \
--cc=stephen_leake@stephe-leake.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).