Summary: | x11-libs/qt-assistant-4.7.4 - loops in make: *** [qch_docs] Interrupt | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Johannes Geiss <johannes.geiss> |
Component: | New packages | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
Johannes Geiss
2012-02-08 19:56:52 UTC
(In reply to comment #0) > Now the process eats 100% CPU and does not continue. 1) What process? Show some output from your favourite process monitoring tool. 2) Please attach the entire build log to this bug report (after you have stopped the build process). Created attachment 301335 [details]
Build log
Output of "top" just before CTRL-C: top - 05:38:29 up 31 days, 14:18, 4 users, load average: 2.03, 2.19, 1.67 Tasks: 185 total, 2 running, 177 sleeping, 6 stopped, 0 zombie Cpu(s): 99.0%us, 1.0%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 1033812k total, 950496k used, 83316k free, 171048k buffers Swap: 2088444k total, 117040k used, 1971404k free, 397840k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ WCHAN COMMAND 20775 root 20 0 52424 40m 3360 R 94.8 4.1 2:16.91 ? /var/tmp/portage/x11-libs/qt-assistant-4.7.4/work/qt-ever 20708 jgeiss 20 0 2736 1248 920 R 0.4 0.1 0:00.34 - top After CTRL-C: top - 05:41:15 up 31 days, 14:21, 4 users, load average: 0.57, 1.54, 1.52 Tasks: 174 total, 1 running, 167 sleeping, 6 stopped, 0 zombie Cpu(s): 5.7%us, 1.0%sy, 0.2%ni, 93.1%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 1033812k total, 893344k used, 140468k free, 171152k buffers Swap: 2088444k total, 117040k used, 1971404k free, 397996k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ WCHAN COMMAND 20708 jgeiss 20 0 2736 1248 920 R 0.1 0.1 0:00.49 - top Er, so that output in comment #3 doesn't actually list the command, only the incomplete path leading up to it. *** This bug has been marked as a duplicate of bug 398885 *** |