index++ crashed with SIGSEGV in __strlen_sse2()

Bug #916164 reported by Fila Kolodny on 2012-01-13
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
swish++ (Ubuntu)
Undecided
Christian

Bug Description

just logging on

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: swish++ 6.1.5-2.1
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
Date: Thu Jan 12 17:54:03 2012
ExecutablePath: /usr/bin/index++
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: /usr/bin/index++ --config-file /usr/share/dhelp/swish++.conf --index-file /var/lib/dhelp/documents.index --follow-links --incremental -
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff2ecba96c1 <__strlen_sse2+17>: movdqu (%rdi),%xmm1
 PC (0x7ff2ecba96c1) ok
 source "(%rdi)" (0x6e65f2655e27e630) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: swish++
StacktraceTop:
 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:32
 ?? ()
 ?? ()
 __libc_start_main (main=0x403c40, argc=8, ubp_av=0x7fffb9c165d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffb9c165c8) at libc-start.c:226
 ?? ()
Title: index++ crashed with SIGSEGV in __strlen_sse2()
UpgradeStatus: Upgraded to precise on 2012-01-10 (2 days ago)
UserGroups:

Fila Kolodny (fila) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x403c40, argc=8, ubp_av=0x7fffb9c165d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffb9c165c8) at libc-start.c:226
 ?? ()
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Fila Kolodny (fila) on 2012-02-06
visibility: private → public
Charles Norrie (norriecb) wrote :

Trying to add a lot of pacakage with the package mnager. 28 were being add and the systm froze.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in swish++ (Ubuntu):
status: New → Confirmed
Changed in swish++ (Ubuntu):
assignee: nobody → Christian (christianmolinabardi)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers