From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Make "skip" work on inline frames
Date: Sat, 19 Oct 2019 04:40:00 -0000 [thread overview]
Message-ID: <VI1PR03MB452851603771A9F8A45E74C9E46F0@VI1PR03MB4528.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <VI1PR03MB4528B9076FC778EF9C0B8B61E46C0@VI1PR03MB4528.eurprd03.prod.outlook.com>
Hmm,
I noticed that the patch does not yet handle
the step <count> correctly, the count is decremented
although the inline frame is skipped and should not be
counted...
Thus I will need to change at least this:
--- a/gdb/infcmd.c
+++ b/gdb/infcmd.c
@@ -1122,7 +1122,6 @@ prepare_one_step (struct step_command_fsm *sm)
set_running (resume_ptid, 1);
step_into_inline_frame (tp);
- sm->count--;
sal = find_frame_sal (frame);
sym = get_frame_function (frame);
@@ -1132,13 +1131,17 @@ prepare_one_step (struct step_command_fsm *sm)
if (sal.line == 0
|| !function_name_is_marked_for_skip (fn, sal))
- return prepare_one_step (sm);
+ {
+ sm->count--;
+ return prepare_one_step (sm);
+ }
}
So I'll send a new patch in a moment.
Thanks.
On 10/18/19 2:52 PM, Bernd Edlinger wrote:
> Hi,
>
> I noticed that skip is not working well on inlined frames which may
> happen in optimized gcc stage3 binary, where step stops at functions
> which are marked for skip, whenever they happen to be in-lined, where
> it is ignored if the frame is marked for skip, thus currently
> skipped frames are only checked when the skipped function
> is not inlined, which is usually only the case in non-optimized builds.
>
>
> Thanks
> Bernd.
>
next prev parent reply other threads:[~2019-10-19 4:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 12:52 Bernd Edlinger
2019-10-19 4:40 ` Bernd Edlinger [this message]
2019-10-20 6:48 ` [PATCHv2] " Bernd Edlinger
2019-10-26 8:06 ` [PING] " Bernd Edlinger
2019-10-27 1:52 ` Simon Marchi
2019-10-27 2:18 ` Simon Marchi
2019-10-30 21:56 ` Bernd Edlinger
2019-10-31 16:42 ` Pedro Alves
2019-10-31 16:53 ` Simon Marchi
2019-10-31 18:00 ` Pedro Alves
2019-10-31 19:19 ` [PATCHv3] " Bernd Edlinger
2019-11-24 11:22 ` [PATCHv4] " Bernd Edlinger
2019-12-01 20:46 ` [PING] " Bernd Edlinger
2019-12-02 2:34 ` Simon Marchi
2019-12-02 16:47 ` [PATCHv5] " Bernd Edlinger
2019-12-03 4:22 ` Simon Marchi
2019-12-14 13:55 ` [PING] " Bernd Edlinger
2019-12-15 0:46 ` Simon Marchi
2019-12-15 11:25 ` [PATCHv6] " Bernd Edlinger
2019-12-15 13:12 ` Simon Marchi
2019-12-15 18:18 ` Bernd Edlinger
2019-12-17 2:01 ` Simon Marchi
2019-12-17 13:00 ` Bernd Edlinger
2019-10-30 20:06 ` [PATCHv2] " Bernd Edlinger
2019-10-30 20:18 ` Simon Marchi
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=VI1PR03MB452851603771A9F8A45E74C9E46F0@VI1PR03MB4528.eurprd03.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=gdb-patches@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