Hello, Tried reproducing it at work (where it first happened on a build server). On my PC at home with 4 cores / 12 thread the bug reproduces always On a 6 core / 12 threads Xeon Server the bug reproduces always On my work PC with 4 cores / 4 threads running in a VMware Instance it doesnt reproduce. All running Debian Stretch with current updates.
Maybe you want to add infos about your system? >From the sample of 3: Hyperthreading or >= 8 threads or runnin on bare metal instead of in a VM could provoke the bug. Further make 4.1 was uploaded to Debian Stretch on 16h january, the issue appeared on 19th january on the server. So disregard what I said about this not being an upstream issue - its actually quite possible. Heres a dump via attached gdb (step wont do anything so it seems that the thread is blocked): (gdb) thread apply all bt Thread 1 (process 12177): #0 0x00007f476c156962 in do_fcntl (fd=1, cmd=7, arg=0x5595eae95ea0) at ../sysdeps/unix/sysv/linux/fcntl.c:31 #1 0x00007f476c156a29 in __GI___libc_fcntl (fd=<optimized out>, cmd=<optimized out>) at ../sysdeps/unix/sysv/linux/fcntl.c:71 #2 0x00005595eac795a7 in output_dump () #3 0x00005595eac753b1 in reap_children () #4 0x00005595eac76224 in new_job () #5 0x00005595eac81a7d in ?? () #6 0x00005595eac8035e in ?? () #7 0x00005595eac80b3e in ?? () #8 0x00005595eac81d9f in update_goal_chain () #9 0x00005595eac67719 in main () further it has a few file handles open (apart from the 3 basic ones): one pipe two temp files which don't exist anymore I`ll have to compile make with debuginfo if you need more (gonna take a few days) Kind Regards. Norbert 2017-02-17 15:24 GMT+01:00 James Cowgill <jcowg...@debian.org>: > Hi, > > On 16/02/17 21:52, Norbert Lange wrote: >> Package: make >> Version: 4.1-9 >> Severity: important >> >> Dear Maintainer, >> >> running the attached Makefile will hang the process, >> if multiple jobs are used then the process wont respond to a >> TERM and has to be killed. >> >> The very same issue is observed with make-guile. >> >> I believe this to not be an upstream bug, since I observed this >> only a couple weeks ago after an upgrade. >> Unfortunatly I can`t pinpoint a date or version. > > I cannot reproduce this bug. > > Also, make has not been updated in testing for almost a year so if it > only started happening recently, something else probably caused it. > > Running 'make -d -O' (although this may be difficult if the bug requires > redirection to /dev/null) or the output or running make inside gdb and > finding where it hangs might help in diagnosing this. > > Thanks, > James > >
