Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Breakpoint commands in MI mode and "backtrace"
Date: Sun, 08 Oct 2017 10:08:00 -0000	[thread overview]
Message-ID: <8360bqt0im.fsf@gnu.org> (raw)

There seems to be a problem with execution of "bt" as part of
breakpoint commands in MI mode: the output of "bt" is not shown.

What I did was invoke GDB as "gdb -i=mi PROGRAM", then set a
breakpoint or a watchpoint in that program, and defined the following
as its breakpoint commands:

  bt
  end

When the breakpoint triggers, I don't see the backtrace.

I tried other commands, like "up" and "print SOME-VARIABLE", and they
do seem to be executed and the output shown.  So why doesn't that
happen with "backtrace"?  Is it a bug or am I missing something?

(FWIW, I also tried using -break-commands, with a similar result: the
backtrace is not shown when the breakpoint triggers.)

This problem prevents "bt" from being useful in breakpoint commands
when running with the Emacs GDB front-end, which uses MI.

Thanks in advance for any pointers.


             reply	other threads:[~2017-10-08 10:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 10:08 Eli Zaretskii [this message]
     [not found] ` <8a3d7153-7486-032f-aabc-6c3453f96459@simark.ca>
2017-10-08 18:27   ` Eli Zaretskii
2017-10-08 19:24     ` Simon Marchi
2017-10-08 20:03       ` Eli Zaretskii
2017-10-09  4:16         ` Simon Marchi
2017-10-09  7:27           ` Eli Zaretskii
2017-10-09  7:52             ` Eli Zaretskii
2017-10-09 12:02               ` Simon Marchi
2017-10-09 12:59                 ` Eli Zaretskii
2017-10-21  8:26                 ` Eli Zaretskii
2017-10-21 14:13                   ` Simon Marchi
2017-10-21 16:27                     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8360bqt0im.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.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