From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH][gdb] Fix hang after ext sigkill
Date: Wed, 25 Mar 2020 10:44:27 -0400 [thread overview]
Message-ID: <a561d966-3e0c-ec9f-2c72-37b3ad58ab4f@simark.ca> (raw)
In-Reply-To: <831161db-85a9-74da-1833-7bab3cc41d15@suse.de>
On 2020-03-25 6:29 a.m., Tom de Vries wrote:
> Here's the updated patch.
Thanks. Some comments about the test:
- Please add a comment at the top to describe briefly what this is testing.
- Please replace the infinite loops with bounded ones (e.g. for (i = 0; i < 300; i++)),
so that the test program eventually exits if something goes wrong and it is allowed to run
freely.
Simon
next prev parent reply other threads:[~2020-03-25 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 20:14 Tom de Vries
2020-03-09 12:52 ` [PING][PATCH][gdb] " Tom de Vries
2020-03-23 19:16 ` [PING^2][PATCH][gdb] " Tom de Vries
2020-03-24 15:35 ` [PATCH][gdb] " Simon Marchi
2020-03-25 10:29 ` Tom de Vries
2020-03-25 14:44 ` Simon Marchi [this message]
2020-03-25 15:51 ` Tom de Vries
2020-03-25 15:57 ` Simon Marchi
2020-04-16 13:28 ` Pedro Alves
2020-04-21 12:38 ` Tom de Vries
2020-04-21 13:42 ` Pedro Alves
2020-09-25 9:39 ` Tom de Vries
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=a561d966-3e0c-ec9f-2c72-37b3ad58ab4f@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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