Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@linaro.org>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Cc: tankut.baris.aktemur@intel.com, alan.hayward@arm.com
Subject: Re: [PATCH 2/2,v3] [AArch64] Test handling of additional brk instruction patterns
Date: Wed, 29 Jan 2020 14:07:00 -0000	[thread overview]
Message-ID: <23182c46-7e3c-f7e8-a91c-c8cc1049bdcd@linaro.org> (raw)
In-Reply-To: <eb5c24bd-bf03-4ab0-7cca-9f7b159fec8f@simark.ca>



On 1/29/20 11:01 AM, Simon Marchi wrote:
> On 2020-01-29 6:30 a.m., Luis Machado wrote:
>>>> +# Number of expected SIGTRAP's to get.  This needs to be kept in sync
>>>> +# with the source file.
>>>> +set expected_traps 3
>>>> +set keep_going 1
>>>> +set count 0
>>>> +set old_timeout $timeout
>>>> +set timeout 10
>>>
>>> Any reason you are changing the timeout?  There is nothing in the test that
>>> looks like it would take time.
>>>
>>
>> If GDB doesn't support one of these instructions, it will be caught in
>> an infinite loop. The reduced timeout will prevent a long wait time
>> until we bail out.
> 
> Ok.  The worry I have with it is that if the target board has raised the timeout
> on purpose, because it's testing with a slow target/link/emulator, then this will
> cancel it.  In this case I'd just leave the timeout as it is.  Normally, GDB won't
> be broken for this test case, so it won't matter.
> 
> Moreover, the timeout here on my x86 machine is 10 seconds by default.  I just checked
> on an AArch64 box on the compile farm, it's 10 there too.  So in which case was it
> useful to set it to 10?
> 

Interesting. In my mind the default was from 30 to 60. Maybe that has 
changed over the years. If the boards are free to set it, then that is 
more desirable.

I'll let it be then.


  reply	other threads:[~2020-01-29 14:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 11:52 [PATCH 0/2,v3][AArch64]Handle " Luis Machado
2020-01-15 11:52 ` [PATCH 1/2,v3] [AArch64] Recognize more program breakpoint patterns Luis Machado
2020-01-21 11:41   ` Alan Hayward
2020-01-29  2:43     ` Luis Machado
2020-01-29  7:50       ` Simon Marchi
2020-01-15 12:18 ` [PATCH 2/2,v3] [AArch64] Test handling of additional brk instruction patterns Luis Machado
2020-01-21 11:57   ` Alan Hayward
2020-01-29  3:19   ` Simon Marchi
2020-01-29 12:25     ` Luis Machado
2020-01-29 14:04       ` Simon Marchi
2020-01-29 14:07         ` Luis Machado [this message]
2020-01-29 14:10           ` Luis Machado
2020-01-29 14:28             ` Simon Marchi
2020-01-29 14:39               ` Luis Machado

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=23182c46-7e3c-f7e8-a91c-c8cc1049bdcd@linaro.org \
    --to=luis.machado@linaro.org \
    --cc=alan.hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=tankut.baris.aktemur@intel.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