Re: [Mono-list] Calling native .so
Hi, On 4/23/07, Miguel de Icaza <[EMAIL PROTECTED]> wrote: > > Does anyone have any other ideas? Is there another way to do this? > > Try this: > > MONO_LOG_LEVEL="debug" MONO_LOG_MASK="dll" mono program.exe On a somewhat related note, is it possible to get the dlopen()/dlsym() error messages that are printed out when you run with MONO_LOG_MASK=dll put into the message field of the DllNotFoundException? That would make debugging these issues a lot easier. Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] [mono-list]DLL Import errors
Hi, On 4/18/07, Eric Morgan <[EMAIL PROTECTED]> wrote: > The library is clearly there, but both mono and this dltest is saying that > it doesn't exist. I've tried copying the library directly into the folder > with dltest, and it still can't find it, even though is literally right > there. Generally the dynamic linker doesn't look in the current directory. It only looks in directories defined in /etc/ld.so.conf, the paths passed in to -rpath at link-time, and the contents of the LD_LIBRARY_PATH variable at run time. If you set LD_LIBRARY_PATH to /home/rengeo/RenegadeGeophysics/SeismicStudioLinux64/lib, is it found? Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Novell Offline?
Hi, On 4/2/07, Joe Audette <[EMAIL PROTECTED]> wrote: > Am I the only one experiencing this or is all of Novell's web sites > down at the moment? > > I can't get to Novell Forge svn or to Novell.com right now. Is it my > isp or are others experiencing this? We've been having really bad network problems all day in the Cambridge office. I'm not sure to what extent this affects our externally-facing machines. Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] ANNOUNCE: Heap-Buddy 0.2
Hi, I'm pleased to announce the release of Heap-Buddy 0.2. This is a bug fix release. Heap-Buddy is a summarizing memory profiling tool for Mono, written by Jon Trowbridge and Ben Maurer. It attaches to special hooks in the Mono runtime and tracks all of the managed memory allocations, every garbage collection, and every heap resize. The statistics are written out into a data file that can then be analyzed by the heap-buddy tool. Changes from 0.1: * Relicensed from GPL to MIT X11. * Fix deadlock problems on SMP machines. (Joe Shaw) * Always write numerical values as little endian. (Chris Seaton) * Write out the number of live objects in the heap resize hook. (Joe) Note! This version changes the format of the file written out to disk, so 0.2 cannot read 0.1 outfiles. You can download the tarball from: http://primates.ximian.com/~joe/heap-buddy-0.2.tar.gz or check the code out of Mono SVN, module heap-buddy. Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Beagle in the Castle
Hey, On Thu, 2006-08-17 at 11:52 +0100, Carlos Ble wrote: > I have written a little controller to use Beagle in MonoRail: > http://www.shidix.com/carlosble/?p=26 Nice! I'm always happy to see people using Beagle in their applications. > Beagle rocks :-) So do you. :) Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] XSP2 SIGSEGV SIGNAL
Hi, Nicolas Cornu wrote: > I got this error while executing my ASP.NET 2 application with Xsp2. I > am testing if my website developpe dunder Visual Studio 2005 run with xsp2. > I don't know if I must post this here. I've seen this most commonly when closing the sqlite connection and then afterward calling a sqlite function with it. The bindings unfortunately aren't that well guarded against this. Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Buggy Windows.Forms
Hi, On Fri, 2006-05-26 at 18:30 +0100, Nikki Locke wrote: > But it is very unusual for a project to recommend deploying the head version > in a mission-critical situation - it is normal to use the version labelled > "stable". What software you deploy into what situations is ultimately your decision. SWF has never been released in anything but an unstable/testing capacity, so in many respects, SVN HEAD can be considered more "stable" than any released version to date. Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mono rpm repositories
Hi, On Tue, 2006-05-23 at 12:18 -0600, Wade Berrier wrote: > Does anyone have anything against having just one mono channel for each > of these services? I'm not aware of any advantages of having multiple > channels. > > Comments, suggestions? >From the old Red Carpet perspective, the reason for having different channels other than a conceptual organizational concept is because it has an impact on dependency resolution. Generally speaking, packages from subscribed channels are preferred over packages from unsubscribed channels, making it fairly easy to have the same software offered in "stable" and "experimental" channels without too much trouble. I don't know if the new libzypp stuff in zmd has this same sort of stuff in its depsolver. The mono channels don't really seem to have a setup like that, so just having one channel for everything is probably fine for the new stuff. Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Garbage collection and memory usage
Hi, On Fri, 2006-04-07 at 17:30 +0100, Gavin Hamill wrote: > We use SMP machines so from what I've read, Heap Buddy will be no help.. If you have a test box, you can just boot up in a UP kernel and it'll work ok. Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Garbage collection and memory usage
Hi, Joshua Tauberer wrote: For whatever reason, I had trouble using heap buddy a while back when I first tried, which led me to trying Nemerle's profiler (and hacking some things into it, which was a good experience even if heap buddy already did the same things). I was able to find and remove many of the biggest object allocators that I found, but I'll give heap buddy a shot again for finding objects that aren't being collected. One thing I noticed is that heap-buddy will lock up pretty much instantly on SMP machines. I think Jon filed a bug about that, but I don't know what it is offhand. Hopefully he can give more info. Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Garbage collection and memory usage
Hi, On Wed, 2006-04-05 at 14:35 -0400, Joshua Tauberer wrote: > Gavin Hamill wrote: > > Having upgraded mono, recompiled > > xsp+mod_mono and restarted apache, 5 hours later RAM use is at 300M > > and I fully expect it to climb higher. > > I'm having the exact same problem, though I've been able to deal with it > by periodically restarting mod-mono-server (typically two or three times > a day). > > As Paolo reminded me this morning, we need to isolate the problem and > submit a test case. I strongly recommend using Heap Buddy for this. We've used it very successfully in identifying problems in Beagle. Whether it's doing large, unnecessary allocations (and fragmenting the heap) or doing allocations that are never collected by the GC (like adding objects to a static hash table), it can help. You can get the source from here: http://blog.trowbridge.org/index.php?p=49 I blogged a bit about using it to identify a big leak in Mono a few weeks ago: http://joeshaw.org/2006/03/17/386 Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Assembly reference
Hi, On Fri, 2006-03-03 at 13:02 +1100, Paddy Joy wrote: > ** (/usr/local/lib/mono/1.0/mcs.exe:9298): WARNING **: The following > assembly referenced from /tmp/mono/trunk/gtk-sharp/vte/vte-sharp.dll > could not be loaded: > Assembly: gtk-sharp(assemblyref_index=3) > Version:2.4.0.0 > Public Key: 35e10195dab3c99f > The assembly was not found in the Global Assembly Cache, a path listed > in the MONO_PATH environment variable, or in the location of the > executing assembly (/tmp/mono/trunk/gtk-sharp/vte/). > > For some reason on my machine adding gtk-sharp.dll to the gac doesn't > fix the problem Your vte-sharp.dll depends exactly upon gtk-sharp, version 2.4.0.0, public key 35e10195dab3c99f. The version you're installing into the GAC must not be this version. You can see what versions you have installed by running "gacutil -l gtk-sharp". Either you need to rebuild your vte-sharp DLL against the gtk-sharp you have in your GAC, or you need to get the exact DLL version it is looking for. Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Re: [Gtk-sharp-list] Important note for SUSE 9.3 Gtk#2 users
Hi, On Fri, 2005-05-20 at 14:29 -0400, Ben Maurer wrote: > To fix this, you need to do the following: > > rug rm gtk-sharp2 > rug ref > rug in gtk-sharp2 You can also install older versions by explicitly specifying the channel, like so: rug ref rug in channel:gtk-sharp2 (where "channel" is the channel name or alias... I couldn't find a link to the server on the downloads page so I'm not sure what it's exactly named.) > PS: RPM know-it-alls might comment "hey, just set an epoch". I did not > want to do that, because it will complicate things for people using > distros that ship rpms for gtk#2 (like SUSE will in the future), for > those using the DAG repo, etc. An epoch is almost never the right thing to do. :) Joe ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mono.Posix.Syscall.passwd patch
On Tue, 2004-09-14 at 18:40 -0400, Loren Bandiera wrote: > Here is my patch for adding a wrapper for getpwnam(3) to > Mono.Posix.Syscall. I tried to model it after stat(). > > result = Syscall.passwd (username, out passwd); My feeling is that you should keep the same name as the syscall, as it's supposed to be a mapping to the POSIX APIs. Joe ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Red Carpet and Fedora Core2
On Mon, 2004-06-07 at 13:26 +0200, [EMAIL PROTECTED] wrote: > I've replace RedHat Fedora Core 1 with Fedora Core 2. > I would install Red Carpet but there isn't any packages for FC2 and the FC1 > packages give me this error: > > What can I do to get Red Carpet for FC2? Vlad built it for FC2 here: http://slightly.off.net/rc-fc2/rcfc2/fedora-2-i386/ ... but I don't think there is a mono channel available yet. (Note that it also does not point to the Ximian servers by default) Joe ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] Novell, SuSE, Mono.
On Sat, 2003-11-08 at 09:30, Bryan Andrews wrote: > So when will we see the first Novell / Suse release? Will it be far off? The acquisition probably won't be completed until January (according to the press release), so it'll be at least that long. And also, SuSE 9 came out fairly recently, so I would suspect that it'd be 6 months or so before another release. Joe ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mono and MAC OS X?
On Wed, 2003-03-26 at 09:40, Paolo Molaro wrote: > The unload feature is not important, so it's a limitation we don't care > about. The RTLD_LOCAL issue is not a show-stopper either. > It would be better if glib had this feature, but: > *) I doubt it would be accepted (doesn't hurt to ask, though) > *) it would take many months for it to get deployed, anyway > > So we need someone to track down this dlcompat library and add support > in the mono runtime to use it instead of gmodule. Any volunteers? You're right, the version I have says that too. Probably the right thing to do, in my opinion, is to make the dyld gmodule backend also handle dylibs in addition to bundles. Deployment I bet is less of an issue... if it can't be upstreamed for glib 2.2 (in favor of glib 2.4), it could probably be added as a patch in fink. Joe ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mono and MAC OS X?
On Tue, 2003-03-25 at 11:08, Paolo Molaro wrote: > *) dllimport: we currently use GModule and the code in glib doesn't > handle shared libraries. Someone should investigate about using dlopen > in GModule or adding a wrapper in mono The main problem here is that mono takes for granted heavily that in ELF shared libraries and loadable modules are the same thing. In Mach-O this isn't the case, so you can't simply call dlopen() on a shared library (-shared passed to the linker). The module has to be built with -bundle. Also, on OS X the dlopen() calls are compatibility wrappers around the native dyld implementation, so using that instead of the dyld implementation in glib2 won't help. I'm not totally sure how to get around these issues when opening something like the gtk shared libraries as "modules" for gtk#, but I am hardly a Mach-O expert... these are just observations I have from using OS X for a few months and trying to build various software on it. Joe ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
