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 16:43:00 -0000 [thread overview]
Message-ID: <83d0l0q02c.fsf@gnu.org> (raw)
In-Reply-To: <20190502085623.35fa3ebe@f29-4.lan> (message from Kevin Buettner on Thu, 2 May 2019 08:56:23 -0700)
> Date: Thu, 2 May 2019 08:56:23 -0700
> From: Kevin Buettner <kevinb@redhat.com>
> Cc: gdb-patches@sourceware.org, simark@simark.ca
>
> > (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>.
>
> I'm not especially surprised that GDB chose a nearby minimal symbol to
> print here. I am surprised at the rather large offsets from that
> symbol, however. In the example that I studied last year, I think
> that the first offset was 0.
In the full disassembly of print_vectorlike, there are many jumps to
print_vectorlike.cold.65, with different offsets. The smallest offset
is indeed zero. So it looks like print_vectorlike.cold.65 is a heap
of all the "cold paths" in print_vectorlike, all of which eventually
lead to emacs_abort. The direct call to that is just one such path.
Let me know if you need help with building the master branch of Emacs.
next prev parent reply other threads:[~2019-05-02 16:43 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
2019-05-02 15:56 ` Kevin Buettner
2019-05-02 16:43 ` Eli Zaretskii [this message]
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=83d0l0q02c.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