From: Eli Zaretskii <eliz@gnu.org>
To: Moritz Wilhelmy <mw-emacs@barfooze.de>
Cc: 31918@debbugs.gnu.org
Subject: bug#31918: 25.3; gud inserts invalid gdb commands
Date: Thu, 21 Jun 2018 17:27:02 +0300 [thread overview]
Message-ID: <831sd0rz9l.fsf@gnu.org> (raw)
In-Reply-To: <871sd1ckvf.fsf@barfooze.de> (message from Moritz Wilhelmy on Wed, 20 Jun 2018 21:34:44 +0200)
> From: Moritz Wilhelmy <mw-emacs@barfooze.de>
> Date: Wed, 20 Jun 2018 21:34:44 +0200
>
> I'm experiencing problems attaching commands to breakpoints with
> gdb/gud. I reproduced this using emacs -q. I also tried to reproduce the
> same behaviour with gdb running inside the terminal, but it did not
> occur, therefore I blame Emacs. ;)
>
> After M-x gdb, I wrote approximately this (unimportant parts elided):
>
> (gdb) br phy_device.c:579
> Breakpoint 2 at 0xc029c468: file drivers/net/phy/phy_device.c, line 579.
> (gdb) commands
> Type commands for breakpoint(s) 2, one per line.
> End with a line saying just "end".
> info args
> >>>>>info locals
> >p/x phy_id
> >p bus->id
> >if addr < 31
> >cont
> >end
> >end
> (gdb) i br
> 2 breakpoint keep y 0xc029c468 in get_phy_device at drivers/net/phy/phy_device.c:579
> breakpoint already hit 1 time
> info args
> 41-stack-info-frame --thread 2
> 42-thread-info --thread 2
> 43-break-list
> info locals
> p/x phy_id
> p bus->id
> if addr < 31
> cont
> end
> (gdb)
>
> What's the deal with these three lines?
>
> 41-stack-info-frame --thread 2
> 42-thread-info --thread 2
> 43-break-list
I tried to reproduce this, but couldn't. Please tell what is your GDB
version. Also, can you provide a complete recipe, including a program
to debug, and all the steps needed to reproduce the issue, preferably
starting from "emacs -Q"?
(The additional commands are commands injected by gdb-mi.el to allow
Emacs display of various information: call-stack, thread information,
etc. But they shouldn't appear in the commands you specified for your
breakpoints, so this is still some kind of problem. I cannot
reproduce it, though.)
Thanks.
next prev parent reply other threads:[~2018-06-21 14:27 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 [this message]
2018-06-23 15:05 ` Moritz Wilhelmy
2018-06-23 15:14 ` Eli Zaretskii
2018-06-23 16:13 ` Moritz Wilhelmy
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=831sd0rz9l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31918@debbugs.gnu.org \
--cc=mw-emacs@barfooze.de \
/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.