soffice.bin crashed with SIGSEGV in *__GI___libc_free()

[João Pinto]

Binary package hint: openoffice.org

The problem randomly happens when closing a sheet after starting oocalc with:
oocalc "-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager" -norestore -nofirststartwizard -nologo

I am developing some python scripts to populate oosheets .

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: openoffice.org-core 1:3.2.0-7ubuntu4.1
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Tue Jul 6 12:02:04 2010
Disassembly: => 0x7f7115c32ed9: Não é possível acessar a memória no endereço 0x7f7115c32ed9
ExecutablePath: /usr/lib/openoffice/program/soffice.bin
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: /usr/lib/openoffice/program/soffice.bin -calc -accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager -norestore -nofirststartwizard -nologo
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=pt_PT.utf8
 LANGUAGE=pt:pt_BR:en
SegvAnalysis:
 Segfault happened at: 0x7f7115c32ed9: Não é possível acessar a memória no endereço 0x7f7115c32ed9
 PC (0x7f7115c32ed9) not located in a known VMA region (needed executable region)!
 source "0x7f7115c32ed9" (0x7f7115c32ed9) not located in a known VMA region (needed readable region)!
SegvReason:
 executing unknown VMA
 reading unknown VMA
Signal: 11
SourcePackage: openoffice.org
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 *__GI___libc_free (mem=<value optimized out>)
Title: soffice.bin crashed with SIGSEGV in *__GI___libc_free()
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare sbuild

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 free () from /lib/libc.so.6

[Chris Cheney (ccheney)]

Failed retrace.

[João Pinto (joaopinto)]

Could you please provide me the instructions on how to get the required trace information ? I don't see the point on setting the bug to invalid without requesting additional info.

Thanks