From: Pedro Alves <pedro@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.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 11:44:00 -0000 [thread overview]
Message-ID: <201103161013.41848.pedro@codesourcery.com> (raw)
In-Reply-To: <20110316093228.GA27281@host1.jankratochvil.net>
On Wednesday 16 March 2011 09:32:28, Jan Kratochvil wrote:
> 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.
Yes, I'm willing to give that a try. I do think your patch solves
it in a way that makes sense: without --once, the default, we leave the
socket open; with --once, we release it as soon as possible, so the user
can still open several debug sessions with the same port, if he's okay
with not being able to reconnect back to the same gdbserver.
--
Pedro Alves
next prev parent reply other threads:[~2011-03-16 10:13 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
2011-03-16 11:44 ` Pedro Alves [this message]
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=201103161013.41848.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