Re: Beagle 1.3-1 configuration on Debian AMD64?
- From: Kevin Kubasik <kevin kubasik net>
- To: Joe Shaw <joeshaw novell com>
- Cc: dashboard-hackers gnome org
- Subject: Re: Beagle 1.3-1 configuration on Debian AMD64?
- Date: Wed, 11 Jan 2006 15:57:55 -0500
=================================================================
> > Got a SIGSEGV while executing native code. This usually indicates
> > a fatal error in the mono runtime or one of the native libraries
> > used by your application.
> > =================================================================
> >
> > Stacktrace:
> >
> > in <0xb> (wrapper managed-to-native)
> > System.Runtime.InteropServices.Marshal:PtrToStringAnsi (intptr)
> >
> > Native stacktrace:
> >
> > mono-beagled(mono_handle_native_sigsegv+0x88) [0x511138]
> > mono-beagled [0x4dffc8]
> > /lib/libpthread.so.0 [0x2aaaab1827a0]
> > /lib/libc.so.6(strlen+0x30) [0x2aaaab58ce60]
> > mono-beagled(mono_string_new+0x39) [0x4a5f79]
> > [0x42b62023]
>
> A segfault makes me think that this isn't a bug in Beagle, but I don't
> have a x86-64 box so I can't really check up on this. Do other
> mono-based apps like Tombody, F-Spot, etc. run? Is anyone else out
> there running Beagle on an Opteron? (Preferably Debian)
>
Also, where are you getting your mono packages? The default debian
repo or else ware? If you want a quick fix, building the latest stable
mono (1.1.12) from source might help, debian is currently making some
major lib changes in unstable/testing.
--
Cheers,
Kevin Kubasik
http://kubasik.net/blog
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]