From: mono-list-boun...@lists.ximian.com [mailto:mono-list-
boun...@lists.ximian.com] On Behalf Of onedevteam.com
running with mono myapp.exe is not an option. I wan't application to be
useful on computers with no mono installed.
I hope you've considered the licensing implications. In
On 5 Aug 2015, at 13:34, Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
From: mono-list-boun...@lists.ximian.com [mailto:mono-list-
boun...@lists.ximian.com] On Behalf Of onedevteam.com
running with mono myapp.exe is not an option. I wan't application to be
useful
On 05/08/15 18:25, Jonathan Mitchell wrote:
On 5 Aug 2015, at 13:34, Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
From: mono-list-boun...@lists.ximian.com [mailto:mono-list-
boun...@lists.ximian.com] On Behalf Of onedevteam.com
running with mono myapp.exe is not an
On 05.08.2015 18:40, Andres G. Aragoneses wrote:
I hope you've considered the licensing implications. In particular,
if you distribute the mono runtime with an application, your
application will need to be GPL.
The runtime is LGPL.
But AFAIU when you use mkbundle you're not linking anymore,
+1
I'll amplify what @Jean-Michel.Perraud said: a howto guide for mixed mode
(C and C#) debugging on Linux is absolutely essential for any serious
development effort.
That's because the apparent lack of debugging capability really slows
development for projects using mono.
For an idea of what
On 5 Aug 2015, at 02:12, jean-michel.perr...@csiro.au wrote:
I am trying to debug C code, mostly to step through the mono runtime itself.
I too would like to debug the Mono runtime itself and so would really, really,
really like to able to build an MDK with debug symbols and source code
You can build the MDK with
https://github.com/mono/bockbuild#the-mono-mac-distribution, but I'm not sure
if that includes debug symbols (I think it does).
-- Alex
From: jonat...@mugginsoft.com
Date: Wed, 5 Aug 2015 18:06:37 +0100
To: Mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev]
Hi,
The above test appears to have started failing after
https://github.com/mono/mono/commit/8f7b98b9b23dd5cc42011cff5c5c31b32ae1b55
6 (at least according to the jenkins log). What I’m seeing is that the obj
pointer being passed to major_copy_or_mark_object_no_evacuation is
0x1:
Further investigation shows the value being set here:
0x80200bb2 is in mono_gc_wbarrier_set_arrayref (sgen-mono.c:171).
166 void
167 mono_gc_wbarrier_set_arrayref (MonoArray *arr, gpointer slot_ptr,
MonoObject* value)
168 {
169 HEAVY_STAT (++stat_wbarrier_set_arrayref);
