From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simon.marchi@polymtl.ca>, Gary Benson <gbenson@redhat.com>
Cc: gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH][gdb/testsuite] Rewrite catch-follow-exec.exp
Date: Tue, 23 Oct 2018 21:05:00 -0000 [thread overview]
Message-ID: <9d0dc535-b053-5063-eb0c-d7bf3e80fe49@suse.de> (raw)
In-Reply-To: <ae40dda3-8c92-015e-2b0d-d673829f90f3@polymtl.ca>
On 10/23/18 11:04 PM, Simon Marchi wrote:
> On 2018-10-15 3:54 p.m., Tom de Vries wrote:
>>> Just wondering. Would it make life easier if we fixed PR 23368, which
>>> is the reason we have to do the test in an unnatural way?
>>
>> Yes.
>
> Hi Tom,
>
> PR 23368 should be fixed now. Do you plan on updating catch-follow-exec.exp
> to be written in a more standard way?
Sure, will do.
Thanks,
- Tom
next prev parent reply other threads:[~2018-10-23 21:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 10:11 Tom de Vries
2018-10-09 13:52 ` Gary Benson
2018-10-09 16:40 ` Tom de Vries
2018-10-10 9:28 ` Gary Benson
2018-10-10 13:29 ` Simon Marchi
2018-10-10 13:44 ` Gary Benson
2018-10-11 7:47 ` Tom de Vries
2018-10-11 8:33 ` Gary Benson
2018-10-13 22:18 ` Simon Marchi
[not found] ` <480ea2be-eac0-8d19-cfe7-93c56b33a7ac@suse.de>
2018-10-15 22:12 ` Simon Marchi
2018-10-23 21:04 ` Simon Marchi
2018-10-23 21:05 ` Tom de Vries [this message]
2018-10-23 22:38 ` Tom de Vries
2018-10-23 23:37 ` Simon Marchi
2018-10-24 11:47 ` Tom de Vries
2018-10-24 12:09 ` [PATCH][gdb/testsuite] Log wait status on process no longer exists error Tom de Vries
2018-10-24 14:05 ` Simon Marchi
2018-12-05 19:35 ` Pedro Franco de Carvalho
2018-10-15 22:12 ` [PATCH][gdb/testsuite] Rewrite catch-follow-exec.exp Simon Marchi
2018-10-16 16:11 ` Tom de Vries
2018-10-16 17:07 ` Tom de Vries
2018-10-16 20:12 ` Simon Marchi
2018-10-17 7:30 ` Upper case test names Tom de Vries
2018-10-17 12:07 ` Simon Marchi
2018-10-18 12:56 ` Tom de Vries
2018-10-18 13:05 ` 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=9d0dc535-b053-5063-eb0c-d7bf3e80fe49@suse.de \
--to=tdevries@suse.de \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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