Ahh, do not worry. I didn't mean you must demand stable use. As it
is written on our wiki, olive is a workplace for unstable stuff,
mostly for .NET 3.0 and later, and hence it cannot be stable by
its nature. When we hack olive, we make some or many changes in
mono (mostly class libs), and we
On Tue, Jul 22, 2008 at 1:31 AM, Zoltan Varga [EMAIL PROTECTED] wrote:
Architectures which _should_ work: x86/amd64/arm/s390/sparc/itanium. I don't
know the status of ppc.
PPC will be ported by me.
Mark
___
Mono-devel-list mailing list
I would like to have my assembly be checked for basic tampering, and it
would appear that .NET's standard signing would automatically solve my
problem, and indeed it does detect trivial changes made with a hex
editor on windows. However, when I do the same thing with mono, runs
without throwing an
Mark,
Am 22.07.2008 um 10:19 schrieb Mark Probst:
On Tue, Jul 22, 2008 at 1:31 AM, Zoltan Varga [EMAIL PROTECTED]
wrote:
Architectures which _should_ work: x86/amd64/arm/s390/sparc/
itanium. I don't
know the status of ppc.
PPC will be ported by me.
Do you already know what parts of
Thanks you all guys for you great work!
I've tested Mono 2.0 RC and filed two bugz (appeared in 2.0) with
test-cases:
https://bugzilla.novell.com/show_bug.cgi?id=409646
https://bugzilla.novell.com/show_bug.cgi?id=411213
Please, if possible, fix both before official release.
Those are very
On Tue, Jul 22, 2008 at 2:06 PM, Andreas Färber [EMAIL PROTECTED] wrote:
Do you already know what parts of the files will need to be changed? Does
this affect, e.g., the whole opcode-to-machine-code translation and thus the
ppc64 port[1] in progress?
I haven't started looking into it, yet, so
Hi Dean,
Was this change approved for the 2.0 branch, or did you commit it to the
branch by accident?
Also, your patch was not complete; Stream.Length can/will also throw a
NotSupportedException when the stream is unseekable. I'll commit a slighty
modified version to SVN HEAD in a few minutes.
On Tue, 22 Jul 2008 21:12:03 +0200
Gert Driesen [EMAIL PROTECTED] wrote:
Hi Dean,
Hey Gert,
Was this change approved for the 2.0 branch, or did you commit it to the
branch by accident?
It was approved.
Also, your patch was not complete; Stream.Length can/will also throw a
On Tue, Jul 22, 2008 at 12:12 PM, Gert Driesen [EMAIL PROTECTED]
wrote:
Also, your patch was not complete; Stream.Length can/will also throw a
NotSupportedException when the stream is unseekable. I'll commit a slighty
modified version to SVN HEAD in a few minutes.
I'm not sure what you man
Dean,
What I meant to say was that both Stream.Length and Stream.Position can
throw a NotSupportedException when the stream is not seekable. I just
changed Deserialize to no longer special-case a non-seekable MemoryStream,
thereby not invoking Stream.Position.
I'll commit a slightly
I think I really cannot fix the profiler init sequence without adding
another hook to the profiler API, to state that the runtime is
sufficiently initialized so that mono_thread_attach can be called
safely.
The reason is the following: I must have the profiler initialized and
the writer thread
11 matches
Mail list logo
