From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13303@debbugs.gnu.org
Subject: bug#13303: 24.2.91; gdb under emacs broken for break commands
Date: Sat, 29 Dec 2012 10:28:16 -0500 [thread overview]
Message-ID: <85bodc27zj.fsf@stephe-leake.org> (raw)
In-Reply-To: <83han5kof7.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 29 Dec 2012 14:55:56 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
Yes, that is what I was expecting.
> It works for me with GDB 7.3 and Emacs 24.2.91 on GNU/Linux;
Sigh. I hate bugs that behave differently on different machines.
My GNU/Linux is Debian Testing; what are you using?
What Windows are you using? I'm on Windows 7; I could try on Windows XP.
> if it doesn't work for you, please tell what happens when you type
> "end" to end the breakpoint commands.
I get another prompt. (that's why there are two 'end's in the bug report).
> So what happens when sending EOF is not really relevant here, IMO.
Right.
Except that it is a workaround for the bug on Debian, if I don't
execute "set interactive-mode off". If it was also a workaround on
Windows, I could live with it.
>> 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.
Any suggestions for debugging this further?
I've confirmed that 'end' works as expected when running gdb from a bash
shell not under emacs.
'end' also works when running gdb in a bash shell under emacs. I guess
that's a mostly functional workaround.
'end' works with Emacs 23, running gdb with --annotate=3; it seems
to be the switch to -i=mi that causes the problem for me.
I tried reading the gdb interface elisp code; it's very dense, so I
didn't get very far, but I could try again. I did confirm that Emacs 24
no longer supports --annotate=3.
--
-- Stephe
next prev parent reply other threads:[~2012-12-29 15:28 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
2012-12-29 15:28 ` Stephen Leake [this message]
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=85bodc27zj.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=13303@debbugs.gnu.org \
--cc=eliz@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.
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).