putty crashed with SIGSEGV in logevent()

[Moti Ochayun]

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: /usr/bin/putty
NonfreeKernelModules: cdrom
Package: putty 0.60-1 [modified: usr/bin/putty]
PackageArchitecture: i386
ProcCmdline: putty
ProcCwd: /home/moti
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: putty
Stacktrace:
 #0 0x08072d36 in logevent ()
 #1 0x080a8b52 in ?? ()
 #2 0x00000000 in ?? ()
StacktraceTop:
 logevent ()
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 14969):
 #0 0x08072d36 in logevent ()
 #1 0x080a8b52 in ?? ()
 #2 0x00000000 in ?? ()
Title: putty crashed with SIGSEGV in logevent()
Uname: Linux moti-desktop 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0x8072d36 <logevent+22>: mov 0xf34(%esi),%eax
 PC (0x08072d36) ok
 source "0xf34(%esi)" (0x00000f34) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA

[Apport retracing service (apport)]

StacktraceTop:logevent (frontend=0x0, string=0x4cb2fa15 "Connection refused") at ../unix/gtkwin.c:214
telnet_closing (plug=0x8168418, error_msg=0x4cb2fa15 "Connection refused", error_code=111,
net_select_result (fd=6, event=1) at ../unix/uxnet.c:1125
select_result (fd=6, event=1) at ../unix/uxsel.c:124
fd_input_func (data=0x0, sourcefd=6, condition=3) at ../unix/gtkwin.c:1258

[Jacob Nevins (0jacobnk-ulp)]

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 will have first appeared in Ubuntu in putty 0.60+2009-04-05-1. So, the current package should not have this bug.

[Will Bickerstaff (willbickerstaff)]

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 there is no further activity here. If someone can confirm the fix that Jacob mentions then please change the status to fix released, or if we can still reproduce this behaviour then please set the status to confirmed.

[Colin Watson (cjwatson)]

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.