scim-bridge crashed with SIGSEGV in scim::Module::unload()

Bug #406717 reported by Rolf Leggewie on 2009-07-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
scim-bridge (Ubuntu)

Bug Description

Binary package hint: scim-bridge

I was calling scim-bridge from the command-line (not sure if I'm not supposed to do that, but then, no problem is supposed to ever segfault). scim was already running at the time.

possible dupes: bug 338217 and bug 199592

I'm running karmic

ProblemType: Crash
Architecture: i386
Date: Thu Jul 30 06:11:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/scim-bridge
NonfreeKernelModules: slamr
Package: scim-bridge-agent 0.4.16-2ubuntu2
ProcCmdline: scim-bridge
 PATH=(custom, user)
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
 Segfault happened at: 0xb64117 <_ZN4scim6Module6unloadEv+23>: mov (%esi),%eax
 PC (0x00b64117) ok
 source "(%esi)" (0x54552e65) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: scim-bridge
 scim::Module::unload() () from /usr/lib/
 scim::Module::~Module() () from /usr/lib/
 ?? ()
 ?? ()
 ?? ()
Title: scim-bridge crashed with SIGSEGV in scim::Module::unload()
Uname: Linux 2.6.31-4-generic i686
UserGroups: adm admin audio cdrom dialout fax floppy fuse lpadmin plugdev scanner src vboxusers video

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers