On Mon, 25 Feb 2002, Bakul Shah wrote:
> > The value of network debugging to me is not that I can
> > avoid buying a serial cable (big deal), it's that I can
> > do the debugging remotely.
>
> Agreed.
>
> > If I'm going to ssh into a local machine and debug from
> > there, then I can use a serial cable.
>
> The serial cable solution does not scale too well when you
> have many people simulteneously debugging multiple kernels.
> If you use 8-port serial cards on a machine and connect every
> other machine's serial console to it, that machine can become
> the bottleneck + even in a lab keeping track of all the
> serial cables etc. can be a pain. For us the ability to log
> in any test machine and debug any other test machine was very
> valuable.
I hook my development machines up in pairs, with com1 and com2
cross connected. com1 -> com2 and visa versa.
tip com2 on any machine gives me the serial console for it's partner.
and gdb looks at com1, expecting to find the serial gdb output coming out
of com2 on it's partner.
Having said that.. network debugging is good, thuogh ai have a suspicion
that the extent of the perturbations made into the system might lead to a
larger class of "heisenbugs", for which a reversion to the serial
cable or even ddb may be required.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
