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 Petersenwrote: > 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 more detailed information with tools like strace(1), > file(1), etc, though. > > Regards, > Alex > > On Mon, Nov 2, 2015 at 8:13 AM, Greg Young wrote: >> Just in general. As an example if someone copies over a 64 bit build >> for a 32 bit installation. >> >> Or if someone has copied files into a bad location. Or if a profiler >> is just not being loaded for some unknown reason. >> >> Crashes have been pretty easy to debug so far. >> >> On Mon, Nov 2, 2015 at 7:51 AM, Alex Rønne Petersen wrote: >>> Hi, >>> >>> Can you be a bit more specific about the issue? Is it a crash or something >>> else? >>> >>> Regards, >>> Alex >>> >>> On Sun, Nov 1, 2015 at 12:41 PM, Greg Young wrote: Is there any good way of debugging profiler loading issues? Greg -- Studying for the Turing test ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list >> >> >> >> -- >> Studying for the Turing test -- Studying for the Turing test ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[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' ./../../class/lib/basic/bare/System.dll (Location of the symbol related to previous error) My installed Mono is 4.0. My build script says: ./autogen.sh --prefix=$PREFIX --disable-nls make make install The error call site is here: = System.Xml.Xsl.Xslt.ScriptClass = public ScriptClass GetScriptClass(string ns, string language, IErrorHelper errorHelper) { #if CONFIGURATION_DEP CompilerInfo compilerInfo; try { compilerInfo = CodeDomProvider.GetCompilerInfo(language); // error CS0117: System.CodeDom.Compiler.CodeDomProvider' does not contain a definition forGetCompilerInfo' Debug.Assert(compilerInfo != null); } catch (ConfigurationException) { // There is no CodeDom provider defined for this language errorHelper.ReportError(/*[XT_010]*/Res.Xslt_ScriptInvalidLanguage, language); return null; } foreach (ScriptClass scriptClass in scriptClasses) { if (ns == scriptClass.ns) { // Use object comparison because CompilerInfo.Equals may throw if (compilerInfo != scriptClass.compilerInfo) { errorHelper.ReportError(/*[XT_011]*/Res.Xslt_ScriptMixedLanguages, ns); return null; } return scriptClass; } } ScriptClass newScriptClass = new ScriptClass(ns, compilerInfo); newScriptClass.typeDecl.TypeAttributes = TypeAttributes.Public; scriptClasses.Add(newScriptClass); return newScriptClass; #else return null; #endif } Thanks J ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
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 out and adding $PREFIX/bin to the path (must have been trying to build against the old assemblies i guess). -- View this message in context: http://mono.1490590.n4.nabble.com/Building-4-2-on-OS-X-tp4666924p4666925.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Building 4.2 on OS X
> On 10 Nov 2015, at 10:01, Numpsywrote: > > 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 download binary but the issue remains. I will hook up a clean 10.10 VM and try a build on it. > 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 out and adding $PREFIX/bin to the path (must have > been trying to build against the old assemblies i guess). > > > > -- > View this message in context: > http://mono.1490590.n4.nabble.com/Building-4-2-on-OS-X-tp4666924p4666925.html > Sent from the Mono - Dev mailing list archive at Nabble.com. > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
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 > "http://keyserver.ubuntu.com/pks/lookup?op=get=0x3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF; > yum-config-manager --add-repo http://download.mono-project.com/repo/centos/ > > wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm > rpm -ivh epel-release-latest-6.noarch.rpm > > On a RHEL 6.7 x86_64 box, fully updated, with EPEL repo installed, and then I > run (as root) I've added some explicit version numbers to the download page. I was under the impression the Centos 7 minimum was clearer, but I was wrong. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list