This sounds great!
Thanks Zoltan,
Thierry Lafage.
Zoltan Varga a écrit :
Hi,
This should now be fixed in SVN HEAD/2.6/2.4 branches, by these commits:
http://lists.ximian.com/pipermail/mono-patches/2010-March/168306.html
Hi,
-Mensaje original-
De: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] En nombre de Jb Evain
Enviado el: viernes, 12 de marzo de 2010 16:23
Para: mono-devel-list; moonlight-list
Asunto: [Mono-dev] mcs build changes for moonlight
I've tried the trunk version and it's still there.
One question regarding the Mono tracing. Do the EXCEPTION traces come
out as soon as the exception is thrown, or when they are handled. I'm
trying to work out from the trace which function is using the disposed
object / throwing the
It's alright, I'm pretty sure it's in TryReceiveRequest somewhere. Is
there any way to get a stack trace for exceptions raised and handled
within the runtime using the tracing? Would they have line numbers in?
Cheers,
Matt.
-Original Message-
From: Matt
Hello,
I noticed that the implementation of System.Random has a couple of flaws:
1.) The algorithm for the random data fails miserably in some of the Diehard
tests (http://i.cs.hku.hk/~diehard/), even
if it is slightly changed in order to generate full 32-bit random values.
2.) It might return
i can successfully build mono and mcs, but mono-basic fails:
...
make[3]: Entering directory
`/Desktop/dev/mono-2-6/mono-basic/tools/extract-source'
MONO_PATH=../../class/lib/bootstrap:$MONO_PATH mono --debug
../../class/lib/bootstrap/vbnc.exe-debug -r:System.Xml.dll -noconfig
I don't think it is doable, but runtime guys might know.
Atsushi Eno
On 2010/03/16 2:24, Matt Dargavel wrote:
It's alright, I'm pretty sure it's in TryReceiveRequest somewhere. Is
there any way to get a stack trace for exceptions raised and handled
within the runtime using the tracing?
