One simple question: Since the build in the mono subdir was successful,
would building within the mcs subdirs be an appropriate troubleshooting
step?
I know that the mcs/jay subdir builds successfully before the overall build
fails; there's an mcs/jay/jay binary that executes. I'm guessing the bui
Hello David,
Based on the crash site, it would seem that we fail to allocate memory from
the OS, which means we have an OOM situation, which we poorly handle as of
right now.
Could you check whether this is the case, whether there are mono instances
that use more memory than expected.
Hey,
You can call mono_pmip (ip) or mono_print_method_from_ip (ip). For going
deeper, you can either unwind the stack manually looking for the return ip’s
on the stack (which will be similar to 0x40013eca), or call
mono_print_thread_dump (0)
Vlad
From: Mono-devel-list on behalf of M
Ja
Just in case, I ran 'make clean' and redid the build.
Link to build log: http://pastebin.com/TBSUNH4x
On Oct 18, 2016 2:20 PM, "Cyd Haselton" wrote:
> From previous conversation:
>
> On Oct 18, 2016 9:08 AM, "Marek Safar" wrote:
>
> Yes, please
>
> On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton
>From previous conversation:
On Oct 18, 2016 9:08 AM, "Marek Safar" wrote:
Yes, please
On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton @gmail.com >wrote:
I've already posted full build logs from root source folder. Do you want
me to also cd to mono, run make and post build logs from that?
I po
Hi all,
If I at a point where I see something like this (gdb) bt
#0 ves_icall_System_IO_MonoIO_Write (handle=, src=, src_offset=, count=, error=) at file-io.c:895
#1 0x40013eca in ?? ()
#2 0x0006 in ?? ()
#3 0x76803ce0 in ?? ()
#4 0x76805668 in ?? ()
#5 0x00
I just started building and testing with mono 4.6.1 and I'm seeing an
intermittent crash (memory corruption?) now during the build. Happens for me
about one time out of ten. Anyone else seeing this or is there a solution
already available that I could patch with? We have a fairly large project w
Do you want me to re-build in root directory and post that log again?
On Oct 18, 2016 11:39 AM, "Cyd Haselton" wrote:
> Forgot to include mono-dev list
>
> The mono build log is fairly large; pastebin may be slow in displaying the
> entire log.
>
> On Oct 18, 2016 11:38 AM, "Cyd Haselton" wrote
Forgot to include mono-dev list
The mono build log is fairly large; pastebin may be slow in displaying the
entire log.
On Oct 18, 2016 11:38 AM, "Cyd Haselton" wrote:
> The mono build log is fairly large; pastebin may be slow in displaying the
> entire log.
>
> On Oct 18, 2016 11:17 AM, "Cyd Ha
Build in mono dir completed successfully
Link to logs: http://pastebin.com/2YwrnFCe
On Oct 18, 2016 10:05 AM, "Cyd Haselton" wrote:
> That's just it; it doesn't fail. I'll post the pastebin links when I have
> them.
>
> On Oct 18, 2016 10:02 AM, "Marek Safar" wrote:
>
>> I'd like to see full
Thanks Marek,
Any input on the logs?
In the meantime I've deleted the build tree and re-downloaded the sources
so that I can start over from scratch.
Don't know if this is relevant but I have noticed that the Makefiles and
various other scripts do not pick up the CONFIG_SHELL and SHELL vars that
No, bootstrap process is not deprecated and it's still actively used
especially when system mono is unavailable or too old.
Marek
On Tue, Oct 18, 2016 at 12:23 PM, Cyd Haselton wrote:
> Ping for any input on pastebin logs (see previous emails) and if
> bootstrapping mcs was/is/will be deprecate
Ping for any input on pastebin logs (see previous emails) and if
bootstrapping mcs was/is/will be deprecated.
On Oct 16, 2016 2:28 PM, "Cyd Haselton" wrote:
> Still troubleshooting, though I'm running out of ideas.
>
> Is it possible bootstrapping mcs was deprecated?
>
> On Oct 15, 2016 6:52 PM,
Hi all,
I found a test case generated IL code:
iconst r3 <- [0]
storei4_membase_reg [sp + 0x34] <- r3
...
add_imm r6 <- sp [0x34]
...
call r3 <- [r3 <- R76] [r4 <- R77] [r5 <- R78] [r6 <- R79] [r7 <- R80] [r8 <-
R81] [r9 <- R82] [r10 <- R83] clobbers: c
I have traced actual executing instruction,
14 matches
Mail list logo
