I think I'm just going to close this out. It's been a few weeks since
Will's comments, and a few months since Jacob's; since he's an upstream
developer I trust Jacob's analysis. Moti, if you encounter this again
on Ubuntu 9.10 or newer, feel free to reopen this bug with further
details.
**
** Changed in: putty (Ubuntu)
Status: New = Fix Released
** Changed in: putty (Ubuntu)
Status: Fix Released = New
--
putty crashed with SIGSEGV in logevent()
https://bugs.launchpad.net/bugs/146680
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Jacob if this is correct we should the change this bugs status to fix
released. Can it be confirmed that the release you indicate does not
exhibit this behaviour, perhaps moti can? although the original bug
report is quite old. I'm going to set this status to Incomplete so as it
will expire if
** Description changed:
Binary package hint: putty
i try to connect to the server whit putty and i get the crash
the server version 7.04 and the client 7.10
ProblemType: Crash
Architecture: i386
Date: Sat Sep 29 12:03:04 2007
DistroRelease: Ubuntu 7.10
ExecutablePath:
I think this must be down to the bug that was fixed upstream in r8304,
2008-11-17. I think that the backend (*telnet_closing():telnet) must
have been freed by notify_remote_exit(), leading to telnet-frontend
being NULL. (Or at least, I can't see how else telnet-frontend ended up
NULL.)
That fix
** Visibility changed to: Public
--
putty crashed with SIGSEGV in logevent()
https://bugs.launchpad.net/bugs/146680
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
