From: Simon Marchi <simark@simark.ca>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCHv2] Make "skip" work on inline frames
Date: Sun, 27 Oct 2019 02:18:00 -0000 [thread overview]
Message-ID: <215bbf9c-4c3c-5cd2-c657-51aa7262f234@simark.ca> (raw)
In-Reply-To: <8fc93db4-8906-4f4e-53f4-225ebfa0115d@simark.ca>
On 2019-10-26 9:52 p.m., Simon Marchi wrote:
> On 2019-10-20 2:48 a.m., Bernd Edlinger wrote:
>> On 10/19/19 6:38 AM, Bernd Edlinger wrote:
>>> 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);
>>> + }
>>> }
>>>
>>>
>>
>> Attached is an updated patch that fixes this issue,
>> and also adds the following after step_into_inline_frame ():
>>
>> frame = get_current_frame ();
>>
>> That I consider safer, since this function calls reinit_frame_cache ().
>> It was probably just by chance that this did not seem to cause any
>> problems for me.
>>
>>
>> Thanks
>> Bernd.
>
> Hi Bernd,
>
> Sorry for the delay. I'll start looking at this patch, but I first need to play with
> it a bit first and get more familiar with that area of the code.
>
> In the mean time, I looked for your name in the copyright assignment list, and don't find
> it. I think this patch is large enough to warrant one Do you already have one in place?
> If not, please follow instructions here:
>
> https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright/request-assign.future
>
> Simon
Oh, and I noticed that the patch doesn't come with a test, we'll need one before getting
the patch in. There are already some skip tests at testsuite/gdb.base/skip*.exp, so I
could very well imagine a new test named gdb.base/skip-inline.exp.
See these pages for details on how to write and run tests:
- https://sourceware.org/gdb/wiki/GDBTestcaseCookbook
- https://sourceware.org/gdb/wiki/TestingGDB
If you can't manage to make a test, at the very least please provide a minimal reproducer
so somebody else will be able to translate that into a test.
Thanks,
Simon
next prev parent reply other threads:[~2019-10-27 2:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 12:52 [PATCH] " Bernd Edlinger
2019-10-19 4:40 ` Bernd Edlinger
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 [this message]
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=215bbf9c-4c3c-5cd2-c657-51aa7262f234@simark.ca \
--to=simark@simark.ca \
--cc=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