On Tue, Jan 13, 2009 at 10:00:10AM +0000, Colin Watson wrote: > On Mon, Jan 12, 2009 at 10:16:38PM +0000, brian m. carlson wrote: > > I determined that the bug is actually in glibc in experimental. The > > errno value is set to ENOSYS. Last time I checked, Linux 2.6.27 had > > working fork(2) and pipe(2) calls, so glibc is doing some pretty > > crackful things. > > > > I also found out that this is not occuring with every popen call, but > > only some of them. Whether the bug occurs is specific to an invocation, > > but every such invocation is reproducible. > > > > Nevertheless, putty should check the return value of popen. Crashing > > when popen fails is not exactly robust. > > Well, it might well have to bail out anyway, but you're right that it > shouldn't segfault.
Simon Tatham has fixed this in PuTTY upstream (r8411). I'm going to be attempting to put together a snapshot release of putty to experimental in the near future, which should be enough to fix this bug given that it's only happening with glibc/experimental. Cheers, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
