Hey folks,
Beagle-0.3.0 contains libbeagle-1.0 which contains several API
changes; among them these 3 function calls were removed. These were
deprecated methods remaining from old times.
beagle_query_add_hit_type (query, AAA);
beagle_query_add_mime_type (query, BBB);
beagle_query_add_source
I have what I'm sure is a minority problem, but would welcome any
suggestions.
I run on a Fedore 6 box which is managed centrally, i.e. I do not have
root privileges. I have been able in the past to install beagle (up
through 0.2.18) by a modest amount of hacking about and installing
other
I run on a Fedore 6 box which is managed centrally, i.e. I do not have
root privileges. I have been able in the past to install beagle (up
through 0.2.18) by a modest amount of hacking about and installing
other things as well, including my own mono-1.2.2.1, in my own local
tree.
But I'm
Hi,
Just to add to what dBera said:
On 12/3/07, Henry S. Thompson [EMAIL PROTECTED] wrote:
produces a segfault with the following trace:
at (wrapper managed-to-native) System.String.InternalAllocateStr
(int) 0x4
at (wrapper managed-to-native) System.String.InternalAllocateStr
(int)
D Bera writes:
I run on a Fedore 6 box which is managed centrally, i.e. I do not have
root privileges. I have been able in the past to install beagle (up
through 0.2.18) by a modest amount of hacking about and installing
other things as well, including my own mono-1.2.2.1, in my own local
Joe Shaw writes:
Could you post the entire output of this crash?
Thanks for looking -- here it is:
MONO_GAC_PREFIX=/group/ltg/projects/lcontrib ./beagle-config BeagleSearch
*** Running uninstalled Config.exe ***
Debug: Loading old config Beagle.Util.NetworkingConfig from networking.xml
at (wrapper managed-to-native) System.String.InternalAllocateStr (int)
0x4
at (wrapper managed-to-native) System.String.InternalAllocateStr (int)
0x
at System.Text.StringBuilder.InternalEnsureCapacity (int) [0x000b1] in
Hi,
On 12/3/07, D Bera [EMAIL PROTECTED] wrote:
at (wrapper managed-to-native) System.String.InternalAllocateStr (int)
0x4
at (wrapper managed-to-native) System.String.InternalAllocateStr (int)
0x
at System.Text.StringBuilder.InternalEnsureCapacity (int) [0x000b1] in
Hi again,
get_machinename() crasher ... where have I seen this before ?
Maybe this ?
https://bugzilla.novell.com/show_bug.cgi?id=MONO82460
Looks like it, yeah. Unfortunately it's a Mono bug, and it seems to
be deep enough in Mono XmlSerializer magic that we can't work around
it.
Oh
Hi,
at Mono.Unix.UnixEnvironment.get_MachineName () [0xb] in
/amd/nfs/hippocampus/disk/ptn057/projects/lcontrib/src/mono-1.2.5.2/mcs/class/Mono.Posix/Mono.Unix/UnixEnvironment.cs:55
at Beagle.Util.NetworkingConfig..ctor () 0x0001d
at (wrapper runtime-invoke)
Hi,
On 12/3/07, D Bera [EMAIL PROTECTED] wrote:
How about I use System.Environment.MachineName instead of
Mono.Unix.UnixEnvironment.MachineName ? Seems to work with long names
too... (I tried with a 24-char name).
Yeah, let's do that. S.E.MachineName just calls gethostname() in an
internal
Problem: For beagle-0.3.0, beagled crashes when started. The stacktraces look
like (once for each backend):
Error: Caught exception while instantiating Files backend
System.Reflection.TargetInvocationException: Exception has been thrown by the
target of an invocation. ---
How about I use System.Environment.MachineName instead of
Mono.Unix.UnixEnvironment.MachineName ? Seems to work with long names
too... (I tried with a 24-char name).
Yeah, let's do that. S.E.MachineName just calls gethostname() in an
internal call in the runtime. M.U.UE.MachineName
13 matches
Mail list logo