Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Daniel Jacobowitz <dan@codesourcery.com>
Subject: Re: [patch] [gdbserver] Fix multi-GB error log files
Date: Wed, 16 Mar 2011 10:20:00 -0000	[thread overview]
Message-ID: <20110316093228.GA27281@host1.jankratochvil.net> (raw)
In-Reply-To: <201103151941.16708.pedro@codesourcery.com>

Hi Pedro,

if the only concern is the late release cycle phase it can wait.  When it
waited so many ears I do not find a need to provide a temporary testsuite-only
fix just to fix the 7.3 gdbserver testsuite.

So the question is whether do you want to fix the racey user-facing behavior
of gdbserver or not, independent of the GDB release cycle.


Thanks,
Jan


On Tue, 15 Mar 2011 20:41:16 +0100, Pedro Alves wrote:
> 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


  reply	other threads:[~2011-03-16  9:32 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
2011-03-16 10:20           ` Jan Kratochvil [this message]
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=20110316093228.GA27281@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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