Re: INTERNAL: Exiting with 2 jobserver tokens available; should be 5!

2016-11-09 Thread Jaak Ristioja
On 09.11.2016 22:58, Paul Smith wrote: > On Wed, 2016-11-09 at 22:42 +0200, Jaak Ristioja wrote: >> I have no ARM experience myself. I don't even know where to look for >> ABI >> documentation. This is the best I can currently get from the core: >> >> (gdb) thread apply all bt full >> >> Thread 1 (

Infinite xrealloc loop?

2016-11-09 Thread Jaak Ristioja
Hi! While debugging the ARM crashes I noticed the following loop in the code: 1) void * xrealloc (void *ptr, unsigned int size) might call OUT_OF_MEM() 2) The OUT_OF_MEM() macro basically calls fatal() with some arguments 3) void fatal (const floc *flocp, size_t len, const char *fmt, ...) m

Re: INTERNAL: Exiting with 2 jobserver tokens available; should be 5!

2016-11-09 Thread Paul Smith
On Wed, 2016-11-09 at 22:42 +0200, Jaak Ristioja wrote: > I have no ARM experience myself. I don't even know where to look for > ABI > documentation. This is the best I can currently get from the core: > > (gdb) thread apply all bt full > > Thread 1 (LWP 15210): > #0  0x0d33b0bc in ?? () > No sym

Re: INTERNAL: Exiting with 2 jobserver tokens available; should be 5!

2016-11-09 Thread Jaak Ristioja
On 09.11.2016 21:44, Paul Smith wrote: > On Wed, 2016-11-09 at 21:31 +0200, Jaak Ristioja wrote: >> I'm attaching[*] the core and the binaries for 4.2.1, but I don't >> know how to debug it myself. > > It's unlikely anyone here will be able to help debug a random ARM core > file (for sure I can't)

Re: INTERNAL: Exiting with 2 jobserver tokens available; should be 5!

2016-11-09 Thread Paul Smith
On Wed, 2016-11-09 at 21:31 +0200, Jaak Ristioja wrote: > I'm attaching[*] the core and the binaries for 4.2.1, but I don't > know how to debug it myself. It's unlikely anyone here will be able to help debug a random ARM core file (for sure I can't).  At the very least we would need a stacktrace f

Re: INTERNAL: Exiting with 2 jobserver tokens available; should be 5!

2016-11-09 Thread Jaak Ristioja
On 09.11.2016 19:55, Paul Smith wrote: > On Wed, 2016-11-09 at 19:29 +0200, Jaak Ristioja wrote: >> GNU Make seems to randomly crash on an Raspberry Pi 2 with >> >>INTERNAL: Exiting with 2 jobserver tokens available; should be 5! >> >> or similar when emerging Gentoo Linux packages using multip

Re: INTERNAL: Exiting with 2 jobserver tokens available; should be 5!

2016-11-09 Thread Paul Smith
On Wed, 2016-11-09 at 19:29 +0200, Jaak Ristioja wrote: > GNU Make seems to randomly crash on an Raspberry Pi 2 with > >    INTERNAL: Exiting with 2 jobserver tokens available; should be 5! > > or similar when emerging Gentoo Linux packages using multiple jobs > (e.g. -j5). The kernel log then ha

INTERNAL: Exiting with 2 jobserver tokens available; should be 5!

2016-11-09 Thread Jaak Ristioja
Hello! GNU Make seems to randomly crash on an Raspberry Pi 2 with INTERNAL: Exiting with 2 jobserver tokens available; should be 5! or similar when emerging Gentoo Linux packages using multiple jobs (e.g. -j5). The kernel log then has lines like Segmentation fault occurred at(nil) in /

Re: Savannah.gnu.org issue tracker status

2016-11-09 Thread Paul Smith
On Mon, 2016-11-07 at 01:35 +0200, Jaak Ristioja wrote: > Some time ago I submitted a bunch of stuff to the issue tracker at > https://savannah.gnu.org/bugs/?group=make but there doesn't seem to > be much activity there. Hi Jaak.  Thanks for those, I did see them.  I hope to have some time between

Re: Unable to run make

2016-11-09 Thread Eli Zaretskii
> From: Steve Alphonse Siani > Date: Wed, 9 Nov 2016 10:39:27 -0500 > > I am unable to run "make" command. I Tried to reinstall everything in another > place but it still print the same > error: > > 1 [main] make 101064 child_info_fork::abort: > D:\Software\omnetpp-4.6\tools\win32\usr\bin\msys

Unable to run make

2016-11-09 Thread Steve Alphonse Siani
Hi, I am unable to run "make" command. I Tried to reinstall everything in another place but it still print the same error: *1 [main] make 101064 child_info_fork::abort: D:\Software\omnetpp-4.6\tools\win32\usr\bin\msys-unistring-2.dll: Loaded to different address: parent(0x6C) != child(0xE7000