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

Bug #114194 reported by eternal1
4
Affects Status Importance Assigned to Milestone
beagle (Ubuntu)
Invalid
Medium
Kevin Kubasik

Bug Description

Binary package hint: beagle

the program never run.

ProblemType: Crash
Architecture: amd64
Date: Sat May 12 06:19:22 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/beagle/BeagleDaemon.exe
InterpreterPath: /usr/bin/mono
Package: beagle 0.2.16.3-0ubuntu4
PackageArchitecture: amd64
ProcCmdline: beagled /usr/lib/beagle/BeagleDaemon.exe --replace --bg
ProcCwd: /home/eternal1
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/eternal1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=es_ES.UTF-8
Signal: 11
SourcePackage: beagle
StacktraceTop:
 ?? () from /lib/libgcc_s.so.1
 _Unwind_Backtrace () from /lib/libgcc_s.so.1
 backtrace () from /lib/libc.so.6
 ?? ()
 ?? ()
Uname: Linux node02 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy kqemu lpadmin plugdev scanner video

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

StacktraceTop:?? () from /lib/libgcc_s.so.1
_Unwind_Backtrace () from /lib/libgcc_s.so.1
backtrace () from /lib/libc.so.6
mono_handle_native_sigsegv (signal=11, ctx=0x41733c60) at mini-exceptions.c:1052
sigsegv_signal_handler (_dummy=11, info=0x41733d90, context=0x41733c60) at mini.c:11108

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in beagle:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Kevin Kubasik (kkubasik) wrote :

This is with an old version of beagle, mono and ubuntu, as well as having no real indication as to its cause. (beyond the inevitable sigsev problem)

Changed in beagle:
assignee: nobody → kkubasik
status: Confirmed → 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.