[prev in list] [next in list] [prev in thread] [next in thread]
List: mono-devel-list
Subject: Re: [Mono-dev] Porting to Haiku OS - out of memory exception
From: Rodrigo Kumpera <kumpera () gmail ! com>
Date: 2012-09-10 15:24:04
Message-ID: CACmR+BAquoX71ewuHSbfbFbR+aB_r2jeRYLQK92QpSw5oTi2QA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Can you debug the process and check what's raising the OOM? It might be
that boehm doesn't work on Haiku.
On Sun, Sep 9, 2012 at 1:04 PM, Stephen <steveh2009@comcast.net> wrote:
>
> I'm trying to port the latest Mono to Haiku OS (most recent nightly build)
> and I've gotten this far:
>
> 1. Made some very minor changes to get Mono to build (thanks to many fixes
> already applied in 2010, but the port was incomplete).
> 2. Pulled down the latest monolite and placed it in the
> .../class/lib/monolite directory
> 3. make EXTERNAL_MCS=.../class/lib/monolite/basic.exe
> 4. In the mono-wrapper file, I added --debug and --trace
>
> The very first file monolite/gmcs.exe tries to build is
> basic-profile-check.exe from
> ./mono/mcs/build/common/basic-profile-check.cs
>
> Here's where I'm stumped. The mono app reports an out of memory
> exception, the ./mini/mono process stays stuck in memory churning the cpus.
>
> I was expecting a full trace report so that I could narrow down the search
> for the problem but no detailed trace is ever emitted. IIRC it was either
> the --debug or --trace option which allowed me to see that there was an out
> of memory exception in the first place (before, I got the ./mini/mono app
> churning without knowing what was going on).
>
> Is there something I can do when compiling the native C-based ./mini/mono
> app to help give me more debug information?
>
> Is there no --trace information emitted because the provided monolite
> gmcs.exe wasn't compiled with an option which help provide it?
>
> Any ideas/help from the Mono development brain trust here would be greatly
> appreciated. Just feed me the kibbles and I'll hobble along to the next
> problem until the darn thing runs.
>
> Thanks,
>
> Steve
>
>
>
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
[Attachment #5 (text/html)]
Can you debug the process and check what's raising the OOM? It might be that \
boehm doesn't work on Haiku.<br><br><div class="gmail_quote">On Sun, Sep 9, 2012 \
at 1:04 PM, Stephen <span dir="ltr"><<a href="mailto:steveh2009@comcast.net" \
target="_blank">steveh2009@comcast.net</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div><div \
style="font-size:12pt;font-family:Arial"><div><br></div><div>I'm trying to port \
the latest Mono to Haiku OS (most recent nightly build) and I've gotten this \
far:</div> <div><br></div><div>1. Made some very minor changes to get Mono to build \
(thanks to many fixes already applied in 2010, but the port was \
incomplete).</div><div>2. Pulled down the latest monolite and placed it in the \
.../class/lib/monolite directory</div> <div>3. make \
EXTERNAL_MCS=.../class/lib/monolite/basic.exe</div><div>4. In the mono-wrapper file, \
I added --debug and --trace</div><div><br></div><div>The very first file \
monolite/gmcs.exe tries to build is basic-profile-check.exe from \
./mono/mcs/build/common/basic-profile-check.cs </div> <div><br></div><div>Here's \
where I'm stumped. The mono app reports an out of memory exception, the \
./mini/mono process stays stuck in memory churning the \
cpus.</div><div><br></div><div>I was expecting a full trace report so that I could \
narrow down the search for the problem but no detailed trace is ever emitted. IIRC \
it was either the --debug or --trace option which allowed me to see that there was an \
out of memory exception in the first place (before, I got the ./mini/mono app \
churning without knowing what was going on).</div> <div><br></div><div>Is there \
something I can do when compiling the native C-based ./mini/mono app to help give me \
more debug information?</div><div><br></div><div>Is there no --trace information \
emitted because the provided monolite gmcs.exe wasn't compiled with an option \
which help provide it?</div> <div><br></div><div>Any ideas/help from the Mono \
development brain trust here would be greatly appreciated. Just feed me the kibbles \
and I'll hobble along to the next problem until the darn thing \
runs.</div><div><br> \
</div><div>Thanks,</div><div><br></div><div>Steve</div><div><br></div><div><br></div>< \
div><br></div></div></div><br>_______________________________________________<br> \
Mono-devel-list mailing list<br> <a \
href="mailto:Mono-devel-list@lists.ximian.com">Mono-devel-list@lists.ximian.com</a><br>
<a href="http://lists.ximian.com/mailman/listinfo/mono-devel-list" \
target="_blank">http://lists.ximian.com/mailman/listinfo/mono-devel-list</a><br> \
<br></blockquote></div><br>
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic