xchat crashed with SIGSEGV in CRYPTO_add_lock()

Bug #552236 reported by Cody A.W. Somerville
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xchat (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: xchat

I clicked quit from the menu, it prompted me if I was sure, I clicked okay and then it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: xchat 2.8.6-4ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Tue Mar 30 22:13:14 2010
Disassembly: => 0x7f061ecc00d0: Cannot access memory at address 0x7f061ecc00d0
ExecutablePath: /usr/bin/xchat
ProcCmdline: xchat
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f061ecc00d0: Cannot access memory at address 0x7f061ecc00d0
 PC (0x7f061ecc00d0) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: xchat
StacktraceTop:
 ?? ()
 CRYPTO_add_lock () from /lib/libcrypto.so.0.9.8
 SSL_set_fd () from /lib/libssl.so.0.9.8
 ?? ()
 ?? ()
Title: xchat crashed with SIGSEGV in CRYPTO_add_lock()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 CRYPTO_add_lock (pointer=0x2cb5008, amount=-1,
 SSL_set_fd (s=0x255ad90, fd=0) at ssl_lib.c:598
 server_cleanup (serv=0x2cb4e80) at server.c:1065
 server_free (serv=0x9) at server.c:1964

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xchat (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in xchat (Ubuntu):
status: New → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

Are you still reproducing this bug? It appears to be happening in libcrypt code - is this system using an encrypted home directory? Any other info that might help in reproducing the bug?

visibility: private → public
Changed in xchat (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :

Not sure if this is still happening since I currently have apport disabled. However, No, system was not using encrypted home directory. I was, however, connected to an IRC server over SSL.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xchat (Ubuntu) because there has been no activity for 60 days.]

Changed in xchat (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.