From: Simon Marchi <simark@simark.ca>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCHv6] Make "skip" work on inline frames
Date: Tue, 17 Dec 2019 02:01:00 -0000 [thread overview]
Message-ID: <d9f3cdfd-b304-4343-e4e8-f6392e4cb08d@simark.ca> (raw)
In-Reply-To: <AM0PR08MB3714D2E1C39213705513BA19E4560@AM0PR08MB3714.eurprd08.prod.outlook.com>
On 2019-12-15 1:18 p.m., Bernd Edlinger wrote:
> On 12/15/19 2:12 PM, Simon Marchi wrote:
>> On 2019-12-15 6:25 a.m., Bernd Edlinger wrote:
>>> On 12/15/19 1:46 AM, Simon Marchi wrote:
>>>> On 2019-12-02 11:47 a.m., Bernd Edlinger wrote:
>>>>> On 12/2/19 3:34 AM, Simon Marchi wrote:
>>>>>> On 2019-11-24 6:22 a.m., Bernd Edlinger wrote:
>>>>>>> This is just a minor update on the patch
>>>>>>> since the function SYMBOL_PRINT_NAME was removed with
>>>>>>> commit 987012b89bce7f6385ed88585547f852a8005a3f
>>>>>>> I replaced it with sym->print_name (), otherwise the
>>>>>>> patch is unchanged.
>>>>>>
>>>>>> Hi Bernd,
>>>>>>
>>>>>> Sorry, I had lost this in the mailing list noise.
>>>>>>
>>>>>> I played a bit with the patch and different cases of figure. I am not able to understand
>>>>>> the purpose of each of your changes (due to the complexity of that particular code), but
>>>>>> I didn't find anything that stood out as wrong to me. Pedro might be able to do a more
>>>>>> in-depth review of the event handling code.
>>>>>>
>>>>>> If the test tests specifically skipping of inline functions, I'd name it something more
>>>>>> descriptive than "skip2.exp", maybe "skip-inline.exp"?
>>>>>>
>>>>>> Unfortunately, your test doesn't pass on my computer (gcc 9.2.0), but neither does the
>>>>>> gdb.base/skip.exp. I am attaching the gdb.log when running your test, if it can help.
>>>>>>
>>>>>> Simon
>>>>>>
>>>>>
>>>>> Hi Simon,
>>>>>
>>>>> I only tested that with gcc-4.8, and both test cases worked with that gcc version.
>>>>>
>>>>> I tried now with gcc-trunk version from a few days ago, and I think I see
>>>>> what you mean.
>>>>>
>>>>> skip2.c (now skip-inline.c) can be fixed by removing the assignment
>>>>> to x in the first line, which is superfluous (and copied from skip.c).
>>>>> But skip.c cannot be fixed this way. I only see a chance to allow
>>>>> the stepping back to main and then to foo happen.
>>>>>
>>>>> Does this modified test case work for you?
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>> Bernd.
>>>>>
>>>>
>>>> Hi Bernd,
>>>>
>>>> Thanks for fixing the skip.exp test at the same time. I'd prefer if this was done as a
>>>> separate patch though, since it's an issue separate from the inline stepping issue you
>>>> were originally tackling.
>>>
>>> Okay, I split that out as a separate patch now.
>>>
>>>>
>>>> So the patch looks good to me if you remove those bits, and fix the following nits:
>>>>
>>>> - Remove "load_lib completion-support.exp" from the test.
>>>> - The indentation in the .exp should use tabs for multiple of 8 columns, instead of just spaces (like you did in the .c).
>>>>
>>>
>>> Done. Also added changelog text, which I forgot previously.
>>>
>>>> A comment I would have on the bits in skip.exp:
>>>>
>>>> # with recent gcc we jump once back to main before entering foo here
>>>> # if that happens try to step a second time
>>>> gdb_test "step" "foo \\(\\) at.*" "step 3" "main \\(\\) at .*" "step"
>>>>
>>>> It's usually not helpful to say "with recent gcc", since it doesn't mean much, especially
>>>> when reading this 10 years from now. Instead, mention the specific gcc version this was
>>>> observed with. Also, begin the sentence with a capital letter and finish with a period.
>>>>
>>>
>>> Done.
>>>
>>>
>>> Is it OK for trunk?
>>
>> That LGTM. I just remembered that your copyright assignment status was unclear, but I looked
>> up your name and saw that you filed one recently.
>>
>> Would you like me to continue pushing your patches for you, or would you prefer to get push
>> access, so you are able to do so when they are approved?
>>
>
> Either way is fine for me.
Ok, I'll push this one. In case you want an account, the form is there, you
can mention me as the person who approved your access.
https://sourceware.org/cgi-bin/pdw/ps_form.cgi
Simon
https://sourceware.org/cgi-bin/pdw/ps_form.cgi
next prev parent reply other threads:[~2019-12-17 2:01 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
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 [this message]
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=d9f3cdfd-b304-4343-e4e8-f6392e4cb08d@simark.ca \
--to=simark@simark.ca \
--cc=bernd.edlinger@hotmail.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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