From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Daniel Jacobowitz <dan@codesourcery.com>
Subject: Re: [patch] [gdbserver] Fix multi-GB error log files
Date: Tue, 15 Mar 2011 20:06:00 -0000 [thread overview]
Message-ID: <201103151941.16708.pedro@codesourcery.com> (raw)
In-Reply-To: <20110315191824.GA1912@host1.jankratochvil.net>
On Tuesday 15 March 2011 19:18:24, Jan Kratochvil wrote:
> To remove the racy case some kind of backward compatibility with current
> setups has to be broken.
No doubt. As I said, I'm not sure there's a single right answer.
I think it'd be prudent to consider such a socket change early in
the release cycle, not late. If you can fix the testsuite with
just the --once change (or something else), then I am suggesting
we consider that (more pressing issue) independently of
fixing this particular race.
> If you want to keep the racy behavior for users (for its other benefits) I can
> propose a patch fixing only the testsuite and not affecting the normal
> gdbserver executions by users in any way.
Sounds like a plan.
--
Pedro Alves
next prev parent reply other threads:[~2011-03-15 19:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 14:23 Jan Kratochvil
2011-03-15 17:48 ` Pedro Alves
2011-03-15 18:04 ` Daniel Jacobowitz
2011-03-15 18:35 ` Jan Kratochvil
2011-03-15 18:48 ` Pedro Alves
2011-03-15 19:28 ` Jan Kratochvil
2011-03-15 20:06 ` Pedro Alves [this message]
2011-03-16 10:20 ` Jan Kratochvil
2011-03-16 11:44 ` Pedro Alves
2011-04-17 14:05 ` [patch] [gdbserver] Fix multi-GB error log files [doc review] Jan Kratochvil
2011-04-17 16:31 ` Eli Zaretskii
2011-04-22 21:42 ` Jan Kratochvil
2011-04-23 6:16 ` Eli Zaretskii
2011-04-23 8:00 ` Jan Kratochvil
2011-04-23 11:09 ` Eli Zaretskii
2011-04-24 8:24 ` Jan Kratochvil
2011-04-24 7:35 ` Eli Zaretskii
2011-04-24 8:04 ` [commit] " Jan Kratochvil
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=201103151941.16708.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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