BuildIndex.exe crashed with SIGSEGV

Bug #125074 reported by John McGuckian
12
Affects Status Importance Assigned to Milestone
beagle (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: beagle

Not exactly sure what triggered the crash, or what application uses BuildIndex

ProblemType: Crash
Architecture: i386
Date: Tue Jul 10 07:32:36 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/beagle/BuildIndex.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: cdrom
Package: beagle 0.2.17-1ubuntu1
PackageArchitecture: i386
ProcCmdline: beagle-build-index /usr/lib/beagle/BuildIndex.exe --target /var/cache/beagle/indexes/applications --disable-directories --disable-on-battery --recursive /usr/share/applications /usr/local/share/applications /opt/gnome/share/applications /opt/kde3/share/applications
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_IE.UTF-8
 LANGUAGE=en_IE:en
Signal: 11
SourcePackage: beagle
Stacktrace: #0 0x081451c4 in ?? () from /lib/ld-linux.so.2
StacktraceTop: ?? () from /lib/ld-linux.so.2
Title: BuildIndex.exe crashed with SIGSEGV
Uname: Linux john-playroom 2.6.20-16-386 #2 Thu Jun 7 20:16:13 UTC 2007 i686 GNU/Linux
UserGroups:

Revision history for this message
John McGuckian (jaymac) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /lib/ld-linux.so.2

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in beagle:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in beagle:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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