From: Pedro Alves <palves@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH, testsuite] Allow function arguments in bp print match in selftest_setup
Date: Thu, 14 Jun 2018 13:52:00 -0000 [thread overview]
Message-ID: <78069162-c9c6-2def-08ba-9d33ed185280@redhat.com> (raw)
In-Reply-To: <25b1dca5-becc-cef5-1583-6750032064af@suse.de>
On 06/14/2018 02:49 PM, Tom de Vries wrote:
> On 06/14/2018 12:45 PM, Pedro Alves wrote:
>> On 06/14/2018 11:21 AM, Tom de Vries wrote:
>>
>>>> [1] Funny, it passes for me (with the fix for stopping at captured_main),
>>>> because the pattern below the one you're touching matches:
>>>>
>>>> -re "Starting program.*Breakpoint \[0-9\]+,.* at .*main.c:.*$function.*$gdb_prompt $" {
>>>> # $function may be inlined, so the program stops at the line
>>>> # calling $function.
>>>> pass "$description"
>>>> }
>>>>
>>>> and it only happens to match because captured_main calls
>>>> captured_main_1 first thing, which coincidentally
>>>> matches "$function.*":
>>>>
>>>> Breakpoint 1, captured_main (data=<optimized out>) at gdb/binutils-gdb/src/gdb/main.c:1147
>>>> 1147 captured_main_1 (context);
>>>>
>>>> That would probably be better "$function .*", with a space,
>>> Right, I observed that as well, and was thinking of this type of fix.
>
>> Please don't be shy about stating those things upfront, makes
>> review easier. :-)
>>
>
> Ack, yeah, sorry about that. I'm currently visiting the Nuremberg
> office, so I'm a bit more distracted than usual.
Really no biggie. Thanks for all the fixes. Hope you're having fun. :-)
Thanks,
Pedro Alves
prev parent reply other threads:[~2018-06-14 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 15:15 Tom de Vries
2018-06-13 12:56 ` Pedro Alves
2018-06-14 10:21 ` Tom de Vries
2018-06-14 10:46 ` Pedro Alves
2018-06-14 13:49 ` Tom de Vries
2018-06-14 13:52 ` Pedro Alves [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=78069162-c9c6-2def-08ba-9d33ed185280@redhat.com \
--to=palves@redhat.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