From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org, simark@simark.ca
Subject: Re: The 'cold' function attribute and GDB
Date: Thu, 02 May 2019 15:23:00 -0000 [thread overview]
Message-ID: <83muk4q3rr.fsf@gnu.org> (raw)
In-Reply-To: <20190502003849.6759d177@f29-4.lan> (message from Kevin Buettner on Thu, 2 May 2019 00:38:49 -0700)
> Date: Thu, 2 May 2019 00:38:49 -0700
> From: Kevin Buettner <kevinb@redhat.com>
> Cc: gdb-patches@sourceware.org, Simon Marchi <simark@simark.ca>
>
> Can you show me what is printed for the following commands?
>
> disassemble print_vectorlike
> x/3i print_vectorlike
> b print_vectorlike
>
> For the disassemble command, I expect both ranges to be displayed.
> The x and b commands should print insns / set a breakpoint on the entry
> pc (which should NOT be the cold address) of the function. If one or more
> of these things aren't happening, then something is going wrong
> somewhere.
Here:
(gdb) disassemble /m print_vectorlike
Dump of assembler code for function print_vectorlike:
Address range 0x11d6521 to 0x11d81d6:
1367 {
0x011d6521 <+0>: push %ebp
0x011d6522 <+1>: mov %esp,%ebp
0x011d6524 <+3>: push %edi
0x011d6525 <+4>: push %esi
0x011d6526 <+5>: push %ebx
0x011d6527 <+6>: sub $0x7c,%esp
[...]
Address range 0x12e1ce5 to 0x12e1f3b:
1824 emacs_abort ();
0x012e1f36 <+593>: call 0x12e7b40 <emacs_abort>
End of assembler dump.
(gdb) x/3i print_vectorlike
0x11d6521 <print_vectorlike>: push %ebp
0x11d6522 <print_vectorlike+1>: mov %esp,%ebp
0x11d6524 <print_vectorlike+3>: push %edi
(gdb) break print_vectorlike
Breakpoint 1 at 0x11d6521: file print.c, line 1367.
Seems to be according to your expectations.
Btw, if I use a source line number whose code is in the 'cold' area,
then I see this:
(gdb) break print.c:1824
Breakpoint 1 at 0x12e1f36: file print.c, line 1824.
(gdb) info line print.c:1824
Line 1824 of "print.c"
starts at address 0x12e1f36 <print_vectorlike.cold.65+593>
and ends at 0x12e1f3b <print_vectorlike.cold.65+598>.
Thanks.
next prev parent reply other threads:[~2019-05-02 15:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 18:59 Eli Zaretskii
2019-05-01 20:17 ` Simon Marchi
2019-05-02 2:51 ` Kevin Buettner
2019-05-02 6:59 ` Eli Zaretskii
2019-05-02 7:26 ` Kevin Buettner
2019-05-02 15:27 ` Eli Zaretskii
2019-05-02 15:59 ` Kevin Buettner
2019-05-02 16:46 ` Eli Zaretskii
2019-05-02 18:08 ` Simon Marchi
2019-05-02 18:47 ` Eli Zaretskii
2019-05-02 18:55 ` Kevin Buettner
2019-05-02 19:32 ` Eli Zaretskii
2019-05-02 19:51 ` Kevin Buettner
2019-05-02 7:06 ` Eli Zaretskii
2019-05-02 7:38 ` Kevin Buettner
2019-05-02 15:23 ` Eli Zaretskii [this message]
2019-05-02 15:56 ` Kevin Buettner
2019-05-02 16:43 ` Eli Zaretskii
2019-05-02 18:25 ` Kevin Buettner
2019-05-02 18:52 ` Eli Zaretskii
2019-05-02 19:13 ` Kevin Buettner
2019-05-02 19:28 ` Eli Zaretskii
2019-05-02 19:45 ` Kevin Buettner
2019-05-02 19:56 ` Eli Zaretskii
2019-05-02 23:30 ` Kevin Buettner
2019-05-04 8:30 ` Eli Zaretskii
2019-05-05 20:04 ` Kevin Buettner
2019-05-06 15:33 ` Eli Zaretskii
2019-05-06 16:24 ` Kevin Buettner
2019-05-02 15:17 ` 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=83muk4q3rr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=simark@simark.ca \
/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