[bug #49114] job.c: Fixed conversion specifier.

2016-09-17 Thread Jaak Ristioja
Additional Item Attachment, bug #49114 (project make): File name: 0005-job.c-Fixed-conversion-specifier.patch Size:0 KB ___ Reply to this item at: ___

[bug #49111] w32: Removed unused telldir() function.

2016-09-17 Thread Jaak Ristioja
URL: Summary: w32: Removed unused telldir() function. Project: make Submitted by: jotik Submitted on: Sat 17 Sep 2016 04:42:48 PM GMT Severity: 3 - Normal Item Group:

[bug #49116] w32/subproc/sub_proc.c: Fixed potential null pointer dereference.

2016-09-17 Thread Jaak Ristioja
URL: Summary: w32/subproc/sub_proc.c: Fixed potential null pointer dereference. Project: make Submitted by: jotik Submitted on: Sat 17 Sep 2016 04:50:18 PM GMT Severity: 3 - Normal

[bug #49112] arscan.c: Fixed printf conversion specifier in TEST mode

2016-09-17 Thread Jaak Ristioja
URL: Summary: arscan.c: Fixed printf conversion specifier in TEST mode Project: make Submitted by: jotik Submitted on: Sat 17 Sep 2016 04:43:57 PM GMT Severity: 3 - Normal

[bug #49113] expand.c: Fixed possible null pointer dereference

2016-09-17 Thread Jaak Ristioja
URL: Summary: expand.c: Fixed possible null pointer dereference Project: make Submitted by: jotik Submitted on: Sat 17 Sep 2016 04:45:51 PM GMT Severity: 3 - Normal Item

[bug #49114] job.c: Fixed conversion specifier.

2016-09-17 Thread Jaak Ristioja
URL: Summary: job.c: Fixed conversion specifier. Project: make Submitted by: jotik Submitted on: Sat 17 Sep 2016 04:46:52 PM GMT Severity: 3 - Normal Item Group: Bug

[bug #49115] read.c: Fixed invariant condition.

2016-09-17 Thread Jaak Ristioja
URL: Summary: read.c: Fixed invariant condition. Project: make Submitted by: jotik Submitted on: Sat 17 Sep 2016 04:48:40 PM GMT Severity: 3 - Normal Item Group: Bug

[bug #49117] [read.c:710]: (warning) Possible null pointer dereference: collapsed

2016-09-17 Thread Jaak Ristioja
URL: Summary: [read.c:710]: (warning) Possible null pointer dereference: collapsed Project: make Submitted by: jotik Submitted on: Sat 17 Sep 2016 04:57:48 PM GMT Severity: 3 - Normal

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 >

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

2016-11-09 Thread Jaak Ristioja
) in /usr/bin/gmake[make:23312] uid/euid:250/250 gid/egid:250/250, parent /bin/bash[sh:23311] uid/euid:250/250 gid/egid:250/250 Is this some known GNU Make bug on ARM? Best regards, Jaak Ristioja ___ Bug-make mailing list Bug-make@gnu.org https

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 eme

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, ...)

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

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

2016-11-11 Thread Jaak Ristioja
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 be

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

2016-11-19 Thread Jaak Ristioja
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!

2016-11-12 Thread Jaak Ristioja
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 f

Control job launch via external program

2022-12-08 Thread Jaak Ristioja
re. Thanks! :) Best regards, Jaak Ristioja [1]: https://stackoverflow.com/questions/11639524/make-j-ram-limits