I recently read with interest
Brian Nickel's project during the Google Summer Of Code on FastCGI (see
http://kerrick.wordpress.com/
and http://mono-soc-2007.googlecode.com/svn/trunk/brian/FastCgi/doc/index.html).
Especially since I am operating in a shared host with Apache 1.3. As
such I cannot
>>> On Wed, Oct 17, 2007 at 9:11 PM, in message
<[EMAIL PROTECTED]>, Paolo Molaro <[EMAIL PROTECTED]> wrote:
> On 10/17/07 Miguel de Icaza wrote:
>>
>> > > 1. execv() is a Dllimport from libc.
>> >
>> > You should use the Process class.
>> >
>> > > 2. This behavior is not consistently seen.
Hello,
I'm trying to use Mono runtime on MIPS architecture. Attached change mend
some problems, but I'm not confident of the changes (especially the 2nd one),
and I want to ask for the review.
1. At first, compilation fails since there is no definition for mips
in mono/mono/utils/mono-membar.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:mono-devel-list-
> [EMAIL PROTECTED] On Behalf Of Stephen A
> Sent: martes, 16 de octubre de 2007 21:58
> To: mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] glibc detected *** mono: double free or
> corruption
>
> > C-cod
Hi,
This is ok to check in.
Zoltan
On 10/17/07, Bill Holmes <[EMAIL PROTECTED]> wrote:
> I ran across some code in my app that marshaled boolean types as U1
> and was receiving a g_warning from the mono runtime. "marshalling
> bool as native type %x is currently not supported"
>
> Cha
Bill Holmes wrote:
> And for my own curiosity of how things work my question is; without
> this patch a boolean marshaled as U1 will go to the default case and
> marshal a 32 bit integer. Will this mess up the arguments passed to
> the C function call because the size being pushed is bigger than t
On 10/17/07 Miguel de Icaza wrote:
>
> > > 1. execv() is a Dllimport from libc.
> >
> > You should use the Process class.
> >
> > > 2. This behavior is not consistently seen.
> > > 3. Application is a daemon process.
> > > 4. mono version used 1.1.13
> >
> > You should use mono 1.2.5 and up.
>
> > 1. execv() is a Dllimport from libc.
>
> You should use the Process class.
>
> > 2. This behavior is not consistently seen.
> > 3. Application is a daemon process.
> > 4. mono version used 1.1.13
>
> You should use mono 1.2.5 and up.
>
> That said, you should post the signature of the met
I ran across some code in my app that marshaled boolean types as U1
and was receiving a g_warning from the mono runtime. "marshalling
bool as native type %x is currently not supported"
Changing my code to I1 is easy enough but I wonder if U1 should be
supported. This patch does that.
I had to l
Hi,
Thanks for the patch. Fixed in SVN revision 87659.
Thanks
Nagappan
Jerome Haltom wrote:
> I wanted to make you all aware of a patch I have provided:
>
> https://bugzilla.novell.com/show_bug.cgi?id=333082
>
> It's very simple and should be easily accepted by somebody who can do
> such things.
Hi,
Thanks for the patch. Fixed in SVN revision 87659.
Thanks
Nagappan
Jerome Haltom wrote:
> Wanted to make the important parties aware of another simple patch I
> have provided.
>
> https://bugzilla.novell.com/show_bug.cgi?id=331953
>
> Another simple one liner.
>
> ___
On 10/16/07 Juraj Skripsky wrote:
> Was the line "expired.Clear ();" left there by accident?
> The following if(..) will never evaluate to true...
Thanks for the catch, fixed in svn.
It's not really a big deal as that code is there just to reduce
memory usage in the case of big spikes in the numbe
On 10/16/07 C S Vadiraj wrote:
> 1. execv() is a Dllimport from libc.
You should use the Process class.
> 2. This behavior is not consistently seen.
> 3. Application is a daemon process.
> 4. mono version used 1.1.13
You should use mono 1.2.5 and up.
That said, you should post the signature of
Err. Seems still running...
http://mono.ximian.com/monobuild/python/monobuild.py/packagestatus?platf
orm=win-4-i386&package=mono&HEAD_or_RELEASE=HEAD
BTW is the start time reported in UTC or +4?
Andy
> -Original Message-
> From: Wade Berrier [mailto:[EMAIL PROTECTED]
> Sent: 16 Octob
C S Vadiraj wrote:
> Hi,
>
> I have a mono application running. We are noticing a strange behavior while
> we spawn a shell script using execv() call from mono application.
> commands in the script seem to fail either with error status 126 or with
> error message "bad interpreter: Argument list
On Wed, 17 Oct 2007 11:18:21 +0200, Juraj Skripsky <[EMAIL PROTECTED]>
scribbled:
> Hi Marek,
Hey Juraj,
> The attached patch fixes a few issues with StaticSiteMapProvider:
>
> - AddNode doesn't check for key dups before adding items to hashtables
> - RemoveNode doesn't remove item from keyToNo
Hi Marek,
The attached patch fixes a few issues with StaticSiteMapProvider:
- AddNode doesn't check for key dups before adding items to hashtables
- RemoveNode doesn't remove item from keyToNode
- full urls (e.g. http://www.google.com) are not supported
And it cleans up a few dirty spots.
May I
Dear Eric,
thank you very much for your detailed information. I will consider your
polling technique. Since I'm not sure whether mono will support serial
events soon, it seems like a good solution for both environments.
Kind regards,
Dries
Engler, Eric wrote:
> -BEGIN PGP SIGNED MESSAGE--
Please, consider creating installers for Win64, too!
Thanks :)
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
19 matches
Mail list logo
