[Mono-dev] Building from Source Fails with mcs: Command not found (Mono-devel-list Digest, Vol 121, Issue 19) (Mono-devel-list Digest, Vol 121, Issue 20)

[Cyd Haselton]

On May 22, 2015 4:02:50 PM CDT, Cyd Haselton <chaselton at gmail.com> wrote:
>
>
>On May 22, 2015 2:54:07 PM CDT, Cyd Haselton <chaselton at gmail.com>
>wrote:
>>
>>
>>On May 22, 2015 8:35:15 AM CDT, Dan Liew <dan at su-root.co.uk> wrote:
>>>On 22 May 2015 at 14:21, Cyd Haselton <chaselton at gmail.com> wrote:
>>>>
>>>>
>>>> On May 22, 2015 7:34:16 AM CDT, Jo Shields <directhex at apebox.org>
>>>wrote:
>>>>>
>>>>>
>>>>>On 22/05/15 01:16, cyd wrote:
>>>>>> Let me back up a few steps before I start troublehooting this.
>>>>>>
>>>>>> Does the monolite build of mono 4.0 support ARM...specifically
>>>ARMv7?
>>>>> If
>>>>>> so, are there any modifications I need to make before running
>>'make
>>>>>&& make
>>>>>> install?'
>>>>>
>>>>>Monolite is CPU-agnostic. It's just bytecode. Mono 4 supports
>ARMv7,
>>>so
>>>>>the question is what instructions are triggering SIGILL
>>>>>_______________________________________________

**snip**

>>>Another way to debug this is run the program under gdb and make sure
>>>you set it up to intercept SIGILL. When gdb catches SIGILL you can
>>>walk through the stack and also examine the assembly to see if
>>>anything looks suspect to you.
>>
>>Hopefully this helps clarify the problem...it's the portion of logcat
>>during the illegal instruction.
>>
>>I'd really rather not have to port gdb
>>
>>I(  317)     #00  pc 001756e4 
>>/data/data/jackpal.androidterm/kbox2/bld/mono/mono-4.0.0/mono/mini/mono-sgen
>>(method_commands_internal+5588)  (DEBUG)
>>
>>I(  317)          bee727ac  00392ebc 
>>/data/data/jackpal.androidterm/kbox2/bld/mono/mono-4.0.0/mono/mini/mono-sgen
>>(do_rehash+336)  (DEBUG)
>>
>>I(  317)          bee727dc  0019f0e4 
>>/data/data/jackpal.androidterm/kbox2/bld/mono/mono-4.0.0/mono/mini/mono-sgen
>>(mono_arch_emit_prolog+2632)  (DEBUG)
>>
>>I(  317)     00008000-00451000 r-x
>>/data/data/jackpal.androidterm/kbox2/bld/mono/mono-4.0.0/mono/mini/mono-sgen
>> (DEBUG)
>>
>>I(  317)     00458000-0045f000 rwx
>>/data/data/jackpal.androidterm/kbox2/bld/mono/mono-4.0.0/mono/mini/mono-sgen
>> (DEBUG)

UPDATE:

addr2line output of the memory(?) areas above:

/bld/mono/mono-4.0.0 $ addr2line -i -C -e mono/mini/mono-sgen 0019f0e4
/bld/mono/mono-4.0.0/mono/mini/tramp-arm.c:465
/bld/mono/mono-4.0.0 $ addr2line -i -C -e mono/mini/mono-sgen 00392ebc
/bld/mono/mono-4.0.0/eglib/src/gslist.c:36
/bld/mono/mono-4.0.0 $ addr2line -i -C -e mono/mini/mono-sgen 001756e4
/bld/mono/mono-4.0.0/mono/mini/debugger-agent.c:8694

I'm going to investigate the files referenced above but if i'm way off-track or barking up the wrong stack please chime in...at this point I'm guessing.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.