Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
	 Luis Machado <luis.machado@linaro.org>
Subject: Re: [PATCH v2] New testcase for PR tui/25126 (staled source cache)
Date: Tue, 11 Feb 2020 16:38:00 -0000	[thread overview]
Message-ID: <87y2t9nkq7.fsf@redhat.com> (raw)
In-Reply-To: <20200211111014.GO4020@embecosm.com> (Andrew Burgess's message of	"Tue, 11 Feb 2020 11:10:14 +0000")

On Tuesday, February 11 2020, Andrew Burgess wrote:

> * Sergio Durigan Junior <sergiodj@redhat.com> [2020-02-10 15:02:20 -0500]:
[...]
>> +close $bkpsrcfd
>> +close $srcfd
>> +file rename -force -- $bkpsrc $srcfile
>> +# Here, we have to wait 1 second because of the way GDB keeps track to
>> +# check whether the binary has changed or not.  GDB uses stat(2) and
>> +# currently checks 'st_mtime', whose precision is measured in
>> +# seconds.  Since the whole file-copying/rename operation can take
>> +# less than 1 second, GDB can mistakenly assume that the binary is
>> +# still the same if we don't wait here.
>
> Maybe rewrite this comment as:
>
>   We have to wait 1 second because of the way GDB checks whether the
>   binary has changed or not.  GDB uses stat(2) and currently checks
>   'st_mtime', whose precision is measured in seconds.  Since the copy,
>   rename, and rebuild can take less than 1 second, GDB might mistakenly
>   assume that the binary is unchanged.
>
> Otherwise this looks good to me and can be applied.

Thanks, I adopted your version of the text and pushed the patch.

f6be87130b5b327075a09c05e78532816f186995

Thank you and Luis for the reviews.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


      reply	other threads:[~2020-02-11 16:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 23:00 [PATCH] " Sergio Durigan Junior
2020-02-07  9:41 ` Luis Machado
2020-02-07 11:47   ` Andrew Burgess
2020-02-07 17:09     ` Sergio Durigan Junior
2020-02-07 19:54       ` Sergio Durigan Junior
2020-02-07 20:11         ` Sergio Durigan Junior
2020-02-08  0:27           ` Andrew Burgess
2020-02-07 20:18         ` Luis Machado
2020-02-08  9:42           ` Luis Machado
2020-02-07 17:07   ` Sergio Durigan Junior
2020-02-10 19:09 ` [PATCH v2] " Sergio Durigan Junior
2020-02-10 19:33   ` Luis Machado
2020-02-10 20:03     ` Sergio Durigan Junior
2020-02-10 20:02 ` Sergio Durigan Junior
2020-02-10 21:55   ` Luis Machado
2020-02-11 11:10   ` Andrew Burgess
2020-02-11 16:38     ` Sergio Durigan Junior [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=87y2t9nkq7.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.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