Re: [patch] [gdbserver] Fix multi-GB error log files

Daniel Jacobowitz
2011-03-15T17:48:26Z

On Tue, Mar 15, 2011 at 05:42:56PM +0000, Pedro Alves wrote:
> 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?

I don't have much of an opinion on this. The current behavior is
somewhat useful; if gdbserver is running, you can't connect to it.
Jan has correctly identified a potential problem if something "steals"
the port while gdbserver is still running, but nothing hits it in
practice except the testsuite.

--
Daniel Jacobowitz
Mentor Graphics