Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite/sim: Remove redundant setting of timeout
Date: Tue, 04 Dec 2018 16:33:00 -0000	[thread overview]
Message-ID: <fb95cd28-0d01-bbf5-5051-15b6a57bb6cd@redhat.com> (raw)
In-Reply-To: <3c7ef445a7a59fa94f8eaee578d24177@polymtl.ca>

On 12/04/2018 04:15 PM, Simon Marchi wrote:
> On 2018-12-04 11:11, Pedro Alves wrote:
>> On 12/04/2018 04:08 PM, Simon Marchi wrote:
>>> That's very confusing, to say the least.
>>
>> Don't shoot the messenger.  :-)
> 
> Hehe, of course.
> 
> In light of this information, I think Andrew's patch is fine.  Do you?
Sort of.  At least with the removing the tail "set timeout" part,
I agree it's not doing anything.

As for the verbose call, we print "Timeout is now ..." messages
in a lot of places, and if you're looking at the log, I think
seeing a "Timeout is now ..." indication without seeing it changed
again reads like the timeout was never restored...

That's a preexisting problem, of course, since currently
we give the impression that we actually changed the timeout
at the end of the function but we actually didn't...

Still, IMHO, one of these would be a better change:

 a) - remove the initial verbose call too, or,
 b) - add "global timeout" at the start of the function, and restore
      the on-entry value on exit.  That way both "Timeout is now ..."
      messages will be truthful.  This is what e.g.,
      testsuiteconfig/sid.exp does.

In either case, there will be no imbalance in the verbose output.

Thanks,
Pedro Alves


  reply	other threads:[~2018-12-04 16:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 11:33 Andrew Burgess
2018-12-04 15:43 ` Simon Marchi
2018-12-04 15:54   ` Pedro Alves
2018-12-04 16:08     ` Simon Marchi
2018-12-04 16:11       ` Pedro Alves
2018-12-04 16:15         ` Simon Marchi
2018-12-04 16:33           ` Pedro Alves [this message]
2018-12-04 21:34             ` Andrew Burgess
2018-12-04 23:03               ` Pedro Alves

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=fb95cd28-0d01-bbf5-5051-15b6a57bb6cd@redhat.com \
    --to=palves@redhat.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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