Bug#250185: Bug#253149: ssh client segfaulting on strongARM -- OpenSSH_3.8p1 Debian (forwarded from Colin Watson)
So a workaround is to build using -O2 on arm (which should be the
default according to Debian policy anyway).
Philip Blundell writes:
> Apparently this problem is triggered by -O3, which ssh has just started
> using. I don't know any more than that at the moment, unfortunately.
>
> p.
>
> On Sun, 2004-06-13 at 12:26, Matthias Klose wrote:
> > Phil,
> >
> > any idea?
> >
> > Matthias
> >
> > ______________________________________________________________________
> > From: Colin Watson <cjwatson@debian.org>
> > To: "Viney, Ulf" <Ulf.Viney@cognos.com>, 253149@bugs.debian.org
> > Cc: control@bugs.debian.org, debian-gcc@lists.debian.org
> > Subject: Re: Bug#253149: ssh client segfaulting on strongARM -- OpenSSH_3.8p1 Debian
> > Date: Mon, 07 Jun 2004 15:29:12 +0100
> >
> > reassign 253149 gcc-3.3
> > severity 253149 important
> > merge 250185 253149
> > thanks
> >
> > On Mon, Jun 07, 2004 at 10:04:31AM -0400, Viney, Ulf wrote:
> > > Package: ssh
> > > Version: 3.8p1-3 (OpenSSH_3.8p1 Debian 1:3.8p1-3, SSH protocols 1.5/2.0,
> > > OpenSSL 0.9.7d 17 Mar 2004)
> > >
> > > Error:
> > > tiger:~/.ssh# ssh -vvv ulf@localhost
> > >
> > > OpenSSH_3.8p1 Debian 1:3.8p1-3, SSH protocols 1.5/2.0, OpenSSL 0.9.7d 17
> > > Mar 2004
> > > debug1: Reading configuration data /etc/ssh/ssh_config
> > > debug2: ssh_connect: needpriv 0
> > > debug1: Connecting to localhost [127.0.0.1] port 22.
> > > debug1: Connection established.
> > > Segmentation fault
> > [...]
> > > Please note that the CPU is a strongARM. The system is a Netwinder
> > > (www.netwinder.org)
> > >
> > > Details:
> > > sshd is working correctly. I can ssh to the box from an x86 sarge or
> > > woody host. I can not ssh from the strongARM box to any other sshd host.
> >
> > This is bug #250185, which appears to be a toolchain bug. I don't know
> > of any resolution yet.
> >
> > Cheers,
> >
> > --
> > Colin Watson [cjwatson@flatline.org.uk]
> >
Reply to: