unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Executing Emacs commands when a gdb breakpoint is hit
Date: Tue, 21 Jan 2020 20:39:44 +0200	[thread overview]
Message-ID: <83o8uwvekv.fsf@gnu.org> (raw)
In-Reply-To: <CANc-5UypWw3bGkgqZ0McHBs15oMu1vrsPzrkzc4HfJ9y6tRH4w@mail.gmail.com> (message from Skip Montanaro on Tue, 21 Jan 2020 12:02:49 -0600)

> From: Skip Montanaro <skip.montanaro@gmail.com>
> Date: Tue, 21 Jan 2020 12:02:49 -0600
> 
> On a more basic topic, I actually seem unable to cleanly terminate the
> series of commands to execute upon hitting a breakpoint. For example, this
> is what I see now (within an Emacs *gud-python* buffer):
> 
> (gdb) comm 2
> Type commands for breakpoint(s) 2, one per line.
> End with a line saying just "end".
> >p c->c_filename
> >p c->u->u_lineno
> >end
> >
> >end
> >  C-c C-cQuit
> 
> That is, I do what it says, end with a line saying just "end", but it
> doesn't terminate. After trying that a second time, I gave up and I broke
> back to the (gdb) prompt with C-c C-c. Seems like a bug to me. I'm using
> 25.2.2 on Ubuntu 18.04.

Upgrade to a newer Emacs.  This problem was fixed in Emacs 26.2.  A
workaround is to use "commands" instead of its short form "comm".



  reply	other threads:[~2020-01-21 18:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 18:02 Executing Emacs commands when a gdb breakpoint is hit Skip Montanaro
2020-01-21 18:39 ` Eli Zaretskii [this message]
2020-01-22 13:48   ` Skip Montanaro
2020-01-22 17:04     ` Eli Zaretskii
2020-01-22 19:55       ` otadmor .
2020-01-22 21:07       ` Skip Montanaro
2020-01-23 14:45         ` Eli Zaretskii
2020-01-23 21:00           ` Skip Montanaro
2020-01-24  8:01             ` Eli Zaretskii
2020-04-07 20:21               ` otadmor .

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=83o8uwvekv.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).