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

Pedro Alves
2011-03-15T18:36:12Z

On Tuesday 15 March 2011 18:04:23, Jan Kratochvil wrote:
> On Tue, 15 Mar 2011 18:42:56 +0100, Pedro Alves wrote:
> > 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).
>
> In such case we can make --once default:

I don't think that's a good idea. When the user does
"disconnect" (, or gdb crashes), we don't want gdbserver to
exit.

>
> On Sun, 06 Mar 2011 12:55:36 +0100, Jan Kratochvil wrote:
> # Also when --once is already introduced it could be made default (that is
> # introduce an option "--permanent" to keep the current behavior). But this
> # changes the behavior of gdbserver which the users may be used to.
>
> It was not made the default just for backward compatibility which you state
> got broken anyway.

I'm confused. Backwards compatibility would be broken by the listen
socket change. But that socket change looked orthogonal
to the --once stuff? Won't either of the changes fix the problem?

--
Pedro Alves