Ubuntu
beagle package

[apport] BeagleDaemon.exe crashed with SIGSEGV in ()

Bug #104271 reported by muhammad on 2007-04-07

Affects		Status	Importance	Assigned to	Milestone
	beagle (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

7.04

ProblemType: Crash
Architecture: amd64
Date: Sat Apr 7 10:59:08 2007
Disassembly: 0x402b26b0:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/beagle/BeagleDaemon.exe
InterpreterPath: /usr/bin/mono
Package: beagle 0.2.16.3-0ubuntu3
PackageArchitecture: amd64
ProcCmdline: beagled /usr/lib/beagle/BeagleDaemon.exe --replace --bg
ProcCwd: /home/muhammad
ProcEnviron:
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=it_IT.UTF-8
Signal: 11
SourcePackage: beagle
StacktraceTop:
?? ()

unlink () from /lib/libc.so.6
?? ()
?? ()
Uname: Linux R3455Ea 2.6.20-14-generic #2 SMP Mon Apr 2 16:32:46 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags:

Revision history for this message

muhammad (amfolli) wrote on 2007-04-07:

Dependencies.txt Edit (5.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (17.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (690 bytes, text/plain; charset="utf-8")
Registers.txt Edit (945 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (396 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (695 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2007-04-09: Symbolic stack trace

Stacktrace.txt (retraced) Edit (359 bytes, text/plain)

StacktraceTop:?? ()

unlinkat () from /lib/libc.so.6
handle_cleanup () at handles.c:186
exit () from /lib/libc.so.6

Revision history for this message

Apport retracing service (apport) wrote on 2007-04-09: Symbolic threaded stack trace

ThreadStacktrace.txt (retraced) Edit (745 bytes, text/plain)

Revision history for this message

Kevin Kubasik (kkubasik) wrote on 2007-04-17:

Thank you for reporting this bug, however, this crash report matches a very common one, and is not specific enough to help us, since apport does not yet include mono stacktraces.

You may choose to file this report again with information from your beagle logs, if so please choose a more accurate title to describe the problem. The following links should help with filing a helpful bug report.

https://help.ubuntu.com/community/Beagle/Debugging

and
http://beagle-project.org/Examining_Log_Files

http://beagle-project.org/Troubleshooting