Bug#253149: ssh client segfaulting on strongARM -- OpenSSH_3.8p1 Debian (forwarded from Colin Watson)

2004-06-20 Thread Martin Michlmayr
* Philip Blundell [EMAIL PROTECTED] [2004-06-13 22:05]: It seems so, yes. I don't know why openssh started using -O3. It doesn't; openssh uses -O2. Are you sure you don't mean openssl? Er, yes, sorry. I do mean openssl. The miscompiled code is in libcrypto. Christoph, are you going

Bug#250185: Bug#253149: ssh client segfaulting on strongARM -- OpenSSH_3.8p1 Debian (forwarded from Colin Watson)

2004-06-13 Thread Matthias Klose
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,

Bug#250185: Bug#253149: ssh client segfaulting on strongARM -- OpenSSH_3.8p1 Debian (forwarded from Colin Watson)

2004-06-13 Thread Philip Blundell
It seems so, yes. I don't know why openssh started using -O3. p. On Sun, 2004-06-13 at 20:11, Matthias Klose wrote: 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

Bug#250185: Bug#253149: ssh client segfaulting on strongARM -- OpenSSH_3.8p1 Debian (forwarded from Colin Watson)

2004-06-13 Thread Colin Watson
On Sun, Jun 13, 2004 at 08:35:08PM +0100, Philip Blundell wrote: On Sun, 2004-06-13 at 20:11, Matthias Klose wrote: 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. So

Bug#253149: ssh client segfaulting on strongARM -- OpenSSH_3.8p1 Debian (forwarded from Colin Watson)

2004-06-13 Thread Philip Blundell
On Sun, 2004-06-13 at 21:45, Colin Watson wrote: On Sun, Jun 13, 2004 at 08:35:08PM +0100, Philip Blundell wrote: On Sun, 2004-06-13 at 20:11, Matthias Klose wrote: Philip Blundell writes: Apparently this problem is triggered by -O3, which ssh has just started using. I don't know