Ubuntu
beagle package

[apport] mono crashed with SIGSEGV

Bug #88370 reported by varogami on 2007-02-27

4

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

Bug Description

Binary package hint: mono

it has been closed alone

ProblemType: Crash
Architecture: i386
Date: Mon Feb 26 18:24:53 2007
Disassembly: 0xb7e4444c:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/mono
Package: mono-jit 1.2.3.1-0ubuntu1
ProcCmdline: beagled-helper --debug /usr/lib/beagle/IndexHelper.exe
ProcCwd: /home/francesco
ProcEnviron:
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
LANG=it_IT.UTF-8
Signal: 11
SourcePackage: mono
Stacktrace:
#0 0xb7e4444c in ?? () from /lib/ld-linux.so.2
#1 0x00000000 in ?? ()
StacktraceTop:
?? () from /lib/ld-linux.so.2
?? ()
Uname: Linux titano 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux

Tags:

Revision history for this message

varogami (varogami) wrote on 2007-02-27:

#1

Dependencies.txt Edit (346 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (11.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (650 bytes, text/plain; charset="utf-8")
Registers.txt Edit (502 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.0 KiB, text/plain; charset="utf-8")

Revision history for this message

dBera (dbera-web) wrote on 2007-03-02:

#2

Can you do this from a terminal

$ export BEAGLE_MONO_DEBUG_FLAG_IS_SET=1
$ beagled --replace --fg

If beagle crashes within 5-10 minutes, paste the terminal output (last 100 lines or so) and attach it to a bug. If it doesnt, from another terminal do "beagle-shutdown" which will stop beagle. Then you can run it the way you normally run it.

Revision history for this message

varogami (varogami) wrote on 2007-03-02: Re: [Bug 88370] Re: [apport] mono crashed with SIGSEGV

#3

2007/3/2, dBera <email address hidden>:
>
> Can you do this from a terminal
>
> $ export BEAGLE_MONO_DEBUG_FLAG_IS_SET=1
> $ beagled --replace --fg
>
> If beagle crashes within 5-10 minutes, paste the terminal output (last
> 100 lines or so) and attach it to a bug. If it doesnt, from another
> terminal do "beagle-shutdown" which will stop beagle. Then you can run
> it the way you normally run it.
>
> --
> [apport] mono crashed with SIGSEGV
> https://launchpad.net/bugs/88370
>
It don't crash

Revision history for this message

dBera (dbera-web) wrote on 2007-03-05:

#4

The crash might be a random one. If you want, there are some instructions at http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login on how to get the mono stacktrace when beagle crashes. We'll appreciate if you follow the steps and help us obtain a mono stacktrace.

Revision history for this message

Kevin Kubasik (kkubasik) wrote on 2007-03-26:

#5

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

Changed in beagle:
status:	Unconfirmed → Rejected

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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