https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89254
Bug ID: 89254
Summary: std.net.curl and std.parallelism unittests hang
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
Assignee: ibuclaw at gdcproject dot org
Reporter: ro at gcc dot gnu.org
Target Milestone: ---
Target: i686-pc-linux-gnu
When building on Linux/i686, the std.net.curl and std.parallelism unitests
hang and never time out. Unfortunately, when trying to investigate with pstack
or gdb, those hang too and need to be killed explicitly.
strace shows
[pid 40000] write(1, "bc_start_main [0xf2a7a742]\n", 27bc_start_main
[0xf2a7a742]
) = 27
[pid 40000] write(1, "??:? ???[0x8049312]\n", 20??:? ???[0x8049312]
) = 20
[pid 40000] rt_sigaction(SIGSEGV, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0},
NULL, 8) = 0
[pid 40000] rt_sigaction(SIGBUS, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0},
NULL, 8) = 0
[pid 40000] futex(0xf2936ba8, FUTEX_WAIT, 40001, NULL
This is ugly because the complete build/test never finishes without manual
investigation. To make things worse, each test is run twice when running a
multilibbed build due to broken multilib handling of libphobos.unittests
(to be reported separately).
