all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Moritz Wilhelmy <mw-emacs@barfooze.de>
To: 31918@debbugs.gnu.org
Subject: bug#31918: 25.3; gud inserts invalid gdb commands
Date: Sat, 23 Jun 2018 18:13:27 +0200	[thread overview]
Message-ID: <87y3f5bhw8.fsf@barfooze.de> (raw)
In-Reply-To: <83tvpttu0c.fsf@gnu.org>


On Sat, Jun 23 2018, Eli Zaretskii wrote:
> GDB 7.0, AFAIK.  But it's possible that some features need a newer
> GDB.

I'll try this as soon as we get this kernel update out of the door.

> If you invoke GDB from the shell with -i=mi, can you reproduce the
> problem?

I did one debug session last week with manually running gdb -i=mi to
verify whether this is the case, and console gdb did not insert these
commands so my debugging session ran without problems.

I also noticed that Linux console output takes the following form on my
setup:
@"console message from the kernel"
These show up in the terminal, but not in gdb-mi inside Emacs, making
Linux debugging with gdb-mi a bit cumbersome at the moment. I think this
is the format that's described in (info "(gdb) GDB/MI Stream Records").

> Also, do these commands appear in "info break" output right after you
> define the breakpoint, or do you need the breakpoint to break a few
> times before that happens?

I'll check on Monday. I think they appeared right away but I might be
wrong.


Best regards,

Moritz





  reply	other threads:[~2018-06-23 16:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 19:34 bug#31918: 25.3; gud inserts invalid gdb commands Moritz Wilhelmy
2018-06-21 14:27 ` Eli Zaretskii
2018-06-23 15:05   ` Moritz Wilhelmy
2018-06-23 15:14     ` Eli Zaretskii
2018-06-23 16:13       ` Moritz Wilhelmy [this message]
2018-06-23 16:31         ` Eli Zaretskii
2019-07-13  3:38           ` Lars Ingebrigtsen

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=87y3f5bhw8.fsf@barfooze.de \
    --to=mw-emacs@barfooze.de \
    --cc=31918@debbugs.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 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.