Re: [Mono-dev] Profiler Loading Issues

I would expect --verbose to give me information like this. On Mon, Nov 2, 2015 at 8:13 AM, Alex Rønne Petersen wrote: > IIRC we just use dlopen(3) to load the profiler. So as far as Mono is > concerned, the best you'll get is the dlerror(3) output. You might be > able to get

Re: [Mono-list] Looking for mono expert to help debug a hanging process

> > I've tried building with debug symbols and attaching gdb to work out > where it's stopped, but gdb segfaults when I try to get a stack trace > for certain threads. Did you try to debug using MonoDevelop integrated debugger? When the problem arises in managed (C#) Code you can debug with IDE.

[Mono-dev] Building 4.2 on OS X

I can build Mono 4.0 64bit on OS X 10.10 without issue. The 4.2 build dies: ./../../external/referencesource/System.Data.SqlXml/System/Xml/Xsl/Xslt/Scripts.cs(117,48): error CS0117: System.CodeDom.Compiler.CodeDomProvider' does not contain a definition forGetCompilerInfo'

Re: [Mono-dev] Building 4.2 on OS X

I've built the 4.2.1.91 tarball successfully on 64bit OSX, though that was using a downloaded 32bit 4.2 build as the compiler. fwiw, when I tried building the latest Git master recently I got some failures due to missing definitions for the new TLS stuff, and it worked after cleaning everything

Re: [Mono-dev] Building 4.2 on OS X

> On 10 Nov 2015, at 10:01, Numpsy wrote: > > I've built the 4.2.1.91 tarball successfully on 64bit OSX, though that was > using a downloaded 32bit 4.2 build as the compiler. > Thanks for that. I tried building the latest 4.2 GitHub branch using the current 32 bit 4.2

Re: [Mono-dev] Buggered yum repo (Mono-devel-list Digest, Vol 127, Issue 9)

On 09/11/15 19:37, Edward Ned Harvey (mono) wrote: > Right now, when I follow the instructions to install mono > http://www.mono-project.com/docs/getting-started/install/linux/#centos-fedora-and-derivatives > > rpm --import >