public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "yangyibiao at nju dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/29775] An valid address cannot be reached in instruction-level stepping
Date: Fri, 11 Nov 2022 08:09:31 +0000	[thread overview]
Message-ID: <bug-29775-4717-2YEYZiJ6JQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29775-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29775

--- Comment #2 from Yibiao Yang <yangyibiao at nju dot edu.cn> ---
(In reply to Tom de Vries from comment #1)
> (In reply to Yibiao Yang from comment #0)
> > (gdb)
> > 7         __builtin_printf ("'ere I am JH\n");
> 
> This is where the address you mention ( 0x000000000040113a ) is reached.
> 
> Because the address is at a line entry, the address is not printed.
> 
> Do "print /x $pc" here and you'll find the address.
> 
> Try for instance the setting:
> ...
> (gdb) set print frame-info location-and-address
> ...
> that forces the address to be printed also at line entries, that'll make it
> easier to keep track at which address you're at (
> https://sourceware.org/gdb/onlinedocs/gdb/Print-Settings.html ).

Got it, thank you very much.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2022-11-11  8:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  6:52 [Bug backtrace/29775] New: " yangyibiao at nju dot edu.cn
2022-11-11  6:52 ` [Bug backtrace/29775] " yangyibiao at nju dot edu.cn
2022-11-11  7:22 ` yangyibiao at nju dot edu.cn
2022-11-11  7:57 ` vries at gcc dot gnu.org
2022-11-11  8:09 ` yangyibiao at nju dot edu.cn [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=bug-29775-4717-2YEYZiJ6JQ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).