[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [DotGNU]The SEE playground has been visited...

From: Gerard Toonstra
Subject: Re: [DotGNU]The SEE playground has been visited...
Date: 01 Jul 2002 08:26:03 +0000

On Mon, 2002-07-01 at 01:41, Gopal V wrote:
> If memory serves me right, Gerard Toonstra wrote:
> > Good thing I did, cause it coredumps :(   tracing it seems to do with
> > GC_ calls. Possibly because it's now in a plugin that's dynamically
> > loaded... some insights would be appreciated (stack problems?)
> I'll take a closer look and try to clean it up a bit (tonight) ...
> I have to say that the code doesn't look pretty ... ie a lot of 
> hardcoded stuff ... but great design .. I think I'll compensate my 
> lack of vision by helping on the code .

Hardcoded stuff?   hmm... do you refer to the #defines or the logging?

> Also I seem to find definite parallels to my pnet_python code .. this
> seems to be faaar easier to do ?.. ( no nasty Object marshalling ...
> or signature mapping ... Heaven !)
> Well chiraz I hope you can do some crypto magic here as well ...

It is much easier. Your code gave many insights, but also ilrun.c is a
very good starting point. Not sure, but I don't think I have explicitly
ILExecLoadFile'd "mscorlib.dll", your wrapper seems to do that.  Is it

Other than that, I wrote a mixmaster remailer Java applet and coded a
few OpenSSL apps.
> > Sadly, my is very bad, so it probably will not allow you to
> > automake and autoconf it at the moment. I suspect it'll complain about
> > path settings that have been hardcoded rather than detected.
> So how do I make a Makefile out of it .... :-( ... I just tried to
> write my own ...

Oh no!  I made a stupid mistake last night.

The tar's got unreasonably big because of configure/.m4 scripts, so I
decided to tar it one level lower in the tree. That doesn't
contain all the stuff required to make it work, it works within the
scope of the higher level one.

Sorry for that, but at least the source doesn't lie :)

> Coredumps and cannot seem to debug it ... my GCC generates some code
> that my gdb does not understand ... (Dwarf2)

I'll need to work on the auto tools configurations. THe project had been
generated from a KDevelop IDE, but it makes more sense to tear it out
now and let it live it's own life :)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]