public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/29236] wrong mapping between address and source line
Date: Thu, 11 Jan 2024 19:34:38 +0000	[thread overview]
Message-ID: <bug-29236-4717-0yTZMo9AZ6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29236-4717@http.sourceware.org/bugzilla/>

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

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ssbssa at sourceware dot org

--- Comment #2 from Hannes Domani <ssbssa at sourceware dot org> ---
As far as I can tell this is part of gdb's magic to make debugging of inline
functions easier to follow.

I've different addresses, but I get a similar result:
```
(gdb) s
13        access (pa);
(gdb) bt -frame-info location-and-address
#0  0x000000013f96253e in main (argc=<optimized out>, argv=<optimized out>) at
gdb-29236.c:13
(gdb) maint info line-table gdb-29236.c
INDEX  LINE   REL-ADDRESS        UNREL-ADDRESS      IS-STMT PROLOGUE-END
...
12     4      0x000000013f96253e 0x000000014000253e
```

And then, I step again:
```
(gdb) s
0x000000013f96253e in access (ptr=<optimized out>) at gdb-29236.c:4
4       void access (volatile char *ptr) { *ptr = 'x'; }
(gdb) bt -frame-info location-and-address
#0  0x000000013f96253e in access (ptr=<optimized out>) at gdb-29236.c:4
#1  0x000000013f96253e in main (argc=<optimized out>, argv=<optimized out>) at
gdb-29236.c:13
```

The address stays the same, so gdb didn't really step, but just faked this for
the user.

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

      parent reply	other threads:[~2024-01-11 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 17:09 [Bug symtab/29236] New: " yangyibiao at nju dot edu.cn
2022-06-09 17:09 ` [Bug symtab/29236] " yangyibiao at nju dot edu.cn
2022-06-09 17:09 ` yangyibiao at nju dot edu.cn
2022-06-12 16:05 ` tromey at sourceware dot org
2024-01-11 19:34 ` ssbssa at sourceware dot org [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-29236-4717-0yTZMo9AZ6@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).