From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Andrew Burgess <andrew.burgess@embecosm.com>,
Joel Brobecker <brobecker@adacore.com>,
Tom de Vries <tdevries@suse.de>
Subject: Re: [PATCH v2 4/4] Skip .cold functions in search_minsyms_for_name
Date: Tue, 1 Jun 2021 16:53:25 +0200 [thread overview]
Message-ID: <AM8PR10MB47088CE08C1003948116AFBEE43E9@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <AM8PR10MB4708980DBC087FAAEF045B34E4209@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM>
This patch is withdrawn since a similar patch was committed now:
commit 17d305ef8f4b5bf20beaaad427490b3c6773909b
Author: Tom de Vries <tdevries@suse.de>
Date: Tue Jun 1 15:25:51 2021 +0200
[gdb/symtab] Ignore cold clones
Bernd.
On 5/30/21 3:59 PM, Bernd Edlinger wrote:
> When a function with the same name is also available,
> that is preferred.
>
> The .cold function is not the external interface.
>
> Fixes 77f2120b200 ("Don't drop static function bp locations w/o debug info")
>
> The motivation for this patch is that I became aware that the "real"
> get_alias_set function (in gcc's cc1) had a two-PC breakpoint
> location with gdb-9 but a three-PC breakpoint location with gdb-10.
> The third breakpoint location was not an entry point but somewhere in the
> error handling, which is named "get_alias_set.cold".
>
> Bisection pointed to the above commit. Prior to this commit the
> static "get_alias_set.cold" was ignored, since there is also a global
> get_alias_set function. Basically the previous behavior was to ignore
> any static function, when there is a global function with the same name.
> The current behavior is to consider a static function and a global
> function with the same name as different entities.
>
> But a function named with ".cold" is not a real function at all.
> It is just a wrapper for all the cold code paths in that function.
> Therefore this patch checks if a function with the same name is
> found and skip the ".cold" overload in that case.
>
> gdb:
> 2020-11-30 Bernd Edlinger <bernd.edlinger@hotmail.de>
>
> * linespec.c (search_minsyms_for_name): Filter .cold functions when
> a real function with the same name is found.
>
> gdb/testsuite:
> 2020-11-30 Bernd Edlinger <bernd.edlinger@hotmail.de>
>
> * gdb.cp/step-and-next-inline-1.exp: New test.
>
> Thanks,
> Bernd.
>
prev parent reply other threads:[~2021-06-01 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 13:59 Bernd Edlinger
2021-06-01 14:53 ` Bernd Edlinger [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=AM8PR10MB47088CE08C1003948116AFBEE43E9@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM \
--to=bernd.edlinger@hotmail.de \
--cc=andrew.burgess@embecosm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).