From: Simon Marchi <simon.marchi@polymtl.ca>
To: Steve Biederman <steve.biederman@synopsys.com>
Cc: gdb@sourceware.org
Subject: Re: gdb not displaying frame info after a "next"
Date: Tue, 23 Oct 2018 20:17:00 -0000 [thread overview]
Message-ID: <9cb146a4656f41c7e470482bddc0eea1@polymtl.ca> (raw)
In-Reply-To: <C51657E211E6EB48AACFF031E78EA7A50238637AD6@US01WEMBX2.internal.synopsys.com>
On 2018-10-09 14:59, Steve Biederman wrote:
> My Linux gdb (8.1 or 7.anything) is no longer automatically showing
> the frame information after
>
> a "next". It knows the frame information; if I follow every "next"
>
> with a "frame", the "frame" command does the right thing, but "next"
>
> all by itself does not print anything but a fresh (gdb) prompt.
>
> Googling has found me no one else who has ever encountered this as far
>
> as my Googling skills can tell.
>
>
>
> How can I debug what the cause and solution is?
GDB will only print the frame if the frame changes, for example if next
causes the program to exit a function:
(gdb) n
5 return pouf;
(gdb)
6 }
(gdb)
main () at test.c:10
10 sleep(2);
Is this what you get? Do you expect something else?
Simon
prev parent reply other threads:[~2018-10-23 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 19:00 Steve Biederman
2018-10-23 20:17 ` Simon Marchi [this message]
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=9cb146a4656f41c7e470482bddc0eea1@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=steve.biederman@synopsys.com \
/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).