Subject: Re: vi broken currently?
To: gabriel rosenkoetter <email@example.com>
From: Nigel Reed <firstname.lastname@example.org>
Date: 11/02/2001 22:14:02
On Fri, Nov 02, 2001 at 10:08:10PM -0500, gabriel rosenkoetter wrote:
> On Sat, Nov 03, 2001 at 03:18:25AM +0100, Feico Dillema wrote:
> > Hmmm, trying to get sshd to segfault remotely is not what I like to
> > do. I''ll try it when I get into my office again. Maybe tomorrow.
> Heh. Fair enough.
> You could just ssh in regularly and start *another* sshd (making use
> of the -p flag), of course. ;^>
> > Does PR 14418 only apply to sshd in debug mode? Without debug mode I
> > don't see any problems with my sshd at least...
> Yeah, I'm not clear on that either.
> Lets find out, shall we?
> Okay, my sshd doesn't seg fault, even if it is in debug mode, so I'd
> say that Nigel's problem is the result of some other oddity on his
> system. (This is important because it means that some basic libc
> stuff is NOT broken, as I had thought it might be, leading to
> segfaults in some cases--sshd--and just complaints in others--vi.)
I didn't get a seg fault, as such...it's just the sshd dumps the client
so no connection can be made. I turned debug on to try and find out
where it was dying.
As soon as I can get -current to build with the new toolchain, I'll
update the pr.