This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] [gdbserver] Fix multi-GB error log files
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, Daniel Jacobowitz <dan at codesourcery dot com>
- Date: Tue, 15 Mar 2011 17:42:56 +0000
- Subject: Re: [patch] [gdbserver] Fix multi-GB error log files
- References: <20110306115536.GA31532@host1.jankratochvil.net>
On Sunday 06 March 2011 11:55:36, Jan Kratochvil wrote:
> This change introduces the listening port to remain open during the default
> gdbserver run for users (when "--once" is not used). This is a change where
> the user can mistakenly connect to the "dead" but still listening port.
It seems that this change stands on its own independently from
the --once stuff. I'm worried about whether this breaks use
cases. E.g., as is, you can spawn several instances of
gdbserver + connect, while only needing to open one port in
your firewall. Or perhaps IDEs are relying on that when
spawning the second (and nth) connections to the same
board (while leaving the previous sessions still running).
Daniel, do you have an opinion?
> But I find the assumption that the port will be available when the user will
> want to reconnect as a worse one than the dead-but-listening port.
I see your point. Not sure if there's a single right answer.
--
Pedro Alves