public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "yangyibiao at outlook dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/27151] Step will skip subsequent statements for malloc functions
Date: Wed, 06 Jan 2021 13:44:47 +0000 [thread overview]
Message-ID: <bug-27151-4717-VKBI773Icb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27151-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27151
--- Comment #5 from Yibiao Yang <yangyibiao at outlook dot com> ---
(In reply to Tom de Vries from comment #2)
> This fixes it:
> ...
> diff --git a/gdb/objfiles.h b/gdb/objfiles.h
> index b9bb80b7a62..2afd2f80154 100644
> --- a/gdb/objfiles.h
> +++ b/gdb/objfiles.h
> @@ -786,7 +786,8 @@ extern int pc_in_section (CORE_ADDR, const char *);
> static inline int
> in_plt_section (CORE_ADDR pc)
> {
> - return pc_in_section (pc, ".plt");
> + return (pc_in_section (pc, ".plt")
> + || pc_in_section (pc, ".plt.sec"));
> }
>
> /* Keep a registry of per-objfile data-pointers required by other GDB
> ...
Thanks a lot. I have try this commit and it indeed fix all similar problems.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-06 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 15:31 [Bug breakpoints/27151] New: " yangyibiao at outlook dot com
2021-01-06 0:57 ` [Bug breakpoints/27151] " yangyibiao at outlook dot com
2021-01-06 12:22 ` vries at gcc dot gnu.org
2021-01-06 12:22 ` vries at gcc dot gnu.org
2021-01-06 12:25 ` vries at gcc dot gnu.org
2021-01-06 12:28 ` vries at gcc dot gnu.org
2021-01-06 13:44 ` yangyibiao at outlook dot com [this message]
2021-01-06 13:53 ` vries at gcc dot gnu.org
2021-01-06 15:37 ` vries at gcc dot gnu.org
2021-01-14 9:35 ` cvs-commit at gcc dot gnu.org
2021-01-14 9:41 ` vries at gcc dot gnu.org
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-27151-4717-VKBI773Icb@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).