Re: [Mono-dev] Mono CI weather report 9/15

This is great, thanks a lot. On Mon, 19 Sep 2016, 3:20 p.m. Andi McClure via Mono-devel-list, < mono-devel-list@lists.dot.net> wrote: > What this is: The Mono team has a CI (continuous integration) system which > builds and runs automated tests on every commit checked in to git > (specifically

Re: [Mono-dev] [macios-devel] Signal-chaining & crash reporters

c.c. the android + monodev email list to keep thosein the loop (other responses have been sent there too) On 16/09/16 19:22, "Miguel de Icaza" wrote: Hello, Thanks for getting these proposals out Rolf. I am not a fan of any of the provided options. We have two issues

Re: [Mono-dev] Problem with mcs build

I ran make distclean, reset some env vars and reran the make, using autogen.sh. This time I got a much different error. Here are the links to the config.log and build.log config.log: http://pastebin.com/Pme5tx4W build log: http://pastebin.com/puCMusV7 On Sep 18, 2016 8:32 PM, "Miguel de Icaza"

Re: [Mono-dev] [android-devel] [macios-devel] Signal-chaining & crash reporters

Hi, > From: Rodrigo Kumpera >   > > Hey guys, > > Exposing signal handlers from managed code is always the wrong solution. > > > > If we're crashing in the runtime, a managed code signal handler has very > little chance of works. It's a scenario we will never even consider > supporting.