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

Hi, sounds like a tough situation and printfs() might be the easiest but I thought I might suggest one other complicated idea :-). Surely someone has put together a cross-compiler for this os/hw combination? the idea of compiling on-device would certainly have been impossibly slow until fairly

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

On Sun, 2016-11-20 at 00:03 +0200, Jaak Ristioja wrote: > So I guess I'll attempt to recompile glibc and run valgrind on the > parent "make -j5" process and see whether that turns up anything. If > not, then I'll try the -fsanitize=address approach. I expect all of this > to take some time (and

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

Hi! On 13.11.2016 07:37, Tim Murphy wrote: > Something like Valgrind might spot some initial problem that doesn't > immediately crash but eventually spirals out of control. I could try valgrind, but (1) I will need to recompile glibc with debug symbols to use it, and (2) I don't have an eternity

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

Something like Valgrind might spot some initial problem that doesn't immediately crash but eventually spirals out of control. It seems to support ARM linux now: "20 October 2016: valgrind-3.12.0 is available. This release supports: X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux,

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

On Fri, 2016-11-11 at 19:41 +0200, Jaak Ristioja wrote: > After examining about 10 more core files, these all point to job.c:519 > and job.c:537, similarly to the above: > >   #0  0x00c2bd74 in child_error (child=0x0, exit_code=0, exit_sig=0, > coredump=0, ignored=0) at job.c:519 >   pre

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

On Sat, 2016-11-12 at 13:06 +0200, Jaak Ristioja wrote: > I'm guessing that PATH_MAX is 4096 on most Linux systems, while the stack is > 8192. There's no way the stack is so small. Virtually no userspace program can run with an 8k stack, regardless of whether they use alloca() or not. I think

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

On 11.11.2016 19:41, Jaak Ristioja wrote: > On 10.11.2016 09:55, Jaak Ristioja wrote: >> 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

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

On 10.11.2016 09:55, Jaak Ristioja wrote: > 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: >>>

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

On Nov 09 2016, Jaak Ristioja wrote: > Is this some known GNU Make bug on ARM? Works fine here: https://build.opensuse.org/project/show/openSUSE:Factory:ARM Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3

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

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

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

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

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

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

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

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

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

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 eme

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

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. -j

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

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