[Dev] Random hang of building process: deedlock in cmake.

Ilya Palachev i.palachev at samsung.com
Fri Jul 11 09:29:22 GMT 2014


Hi, Vitaly.
Maybe your backtrace information will be somehow more useful if you 
download and unrpm
"debuginfo" and "debugsource" rpm packages from the repository that you 
use as default repository in your ~/.gbs.conf

If you use native gdb (not in chroot) these RPMs should be unrpm'ed 
inside root (/) directory, so that new files
will appear in directories /usr/lib/debug and /usr/src/debug.

I have already noticed cmake's hanging in our build system for many 
times about 2 yours ago. Maybe it's specific for our environment.

Also the output log of cmake will be useful. Does cmake hangs during the 
search of some libraries?

Best regards,
Ilya Palachev
------------------------------------------------------------------------

*From:* Vitaly Chernooky <vitalii.chernookyi at globallogic.com>
*Sent:* Friday, July 11, 2014 1:15PM
*To:* cmake-developers at cmake.org, dev at lists.tizen.org <dev at lists.tizen.org>
*Cc:* Andrii Anisov <andrii.anisov at globallogic.com>
*Subject:* [Dev] Random hang of building process: deedlock in cmake.

Hi all!

Today I caught again a hang of local building process.

I used debugger and strace in steps to catch a bug.

so:

$ pstree
...
      |      |  ??gbs???sh???depanneur???sh???sudo???build???perl
      ?      ?                         ? 
??su???rpmbuild???sh???cmake???gmake
...
$ ps ax | grep gmake
...
1105 ?        Z      0:00 [gmake] <defunct>
...
$ ps ax | grep cmake
...
   760 ?        S      0:01 /usr/bin/cmake ...
...
$ sudo strace -p 760
[sudo] password for vitalii.chernookyi:
Process 760 attached - interrupt to quit
select(4, [3], NULL, NULL, NULL^C <unfinished ...>
Process 760 detached
$ ls -l /proc/760/fd/3
lr-x------ 1 vitalii.chernookyi tizendev 64 Jul 11 11:41 /proc/760/fd/3 
-> pipe:[1670438]
$ ls -l /proc/*/fd/* | grep 'pipe:\[1670438\]'
lr-x------ 1 vitalii.chernookyi tizendev 64 Jul 11 11:41 /proc/760/fd/3 
-> pipe:[1670438]
l-wx------ 1 vitalii.chernookyi tizendev 64 Jul 11 11:42 /proc/760/fd/4 
-> pipe:[1670438]
$ sudo gdb -p 760
...
0x0000000060138543 in ?? ()
(gdb) bt
#0  0x0000000060138543 in ?? ()
#1  0x000000006004a4ce in ?? ()
#2  0x000000006004e2fe in ?? ()
#3  0x0000000060040309 in ?? ()
#4  0x00000000600039ee in ?? ()
#5  0x00000000600d9584 in ?? ()
#6  0x0000000060003f41 in ?? ()
#7  0x00007fff61dc5e88 in ?? ()
#8  0x0000000000000000 in ?? ()
(gdb) quit
...
$


So we caught a deedlock.

Do anyone have any idea how to fix it?


-- 
*Vitaly Chernooky | Senior Developer - Product Engineering and Development*
GlobalLogic
P _+380.44.4929695 ext.1136_ M _+380.98.7920568_ S cvv_2k
www.globallogic.com <http://www.globallogic.com>

http://www.globallogic.com/email_disclaimer.txt


_______________________________________________
Dev mailing list
Dev at lists.tizen.org
https://lists.tizen.org/listinfo/dev



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tizen.org/pipermail/dev/attachments/20140711/7cd033e2/attachment.html>


More information about the Dev mailing list