❦ 18 août 2013 22:53 CEST, Tom Lee <debian@tomlee.co> :
> Ah, the Debug.Log hang seems like it might relate to a missing
> /proc/self/exe symlink -- probably because I didn't mount the /proc
> filesystem. Here's the relevant bit of strace output:
>
> [pid 7463] write(3, "[ OK ] Exception.Exception"..., 143 <unfinished ...>
> [pid 13045] readlink("/proc/self/exe", <unfinished ...>
> [pid 7463] <... write resumed> ) = 143
> [pid 13045] <... readlink resumed> 0x7fff11d94460, 512) = -1 ENOENT
> (No such file or directory)
> [pid 7463] read(0, "[ RUN ] Debug.Log\n", 8192) = 23
> [pid 7463] write(1, "[ RUN ] Debug.Log\n", 23[ RUN ] Debug.Log
> ) = 23
> [pid 13045] futex(0x2aaaabaa75e0, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
> [pid 7463] write(3, "[ RUN ] Debug.Log\n", 23) = 23
> [pid 7463] read(0,
>
> The last two futex(...) & read(...) calls wait around forever.
>
> Might be a silly question, but I'm guessing it's standard practice to
> mount /proc when doing these chrooted builds?
>
> And assuming the build servers are using a chroot, can I also assume
> they will mount procfs on /proc prior to executing a build?
>
> Either way, I'm going to mount /proc in my chroot & try again.
Yes, you can count on /proc being present. And you should really try
pbuilder or cowbuilder. This is just a matter of doing:
cowbuilder --create
cowbuilder --update
cowbuilder --build your.dsc
--
panic("Oh boy, that early out of memory?");
2.2.16 /usr/src/linux/arch/mips/mm/init.c
Attachment:
signature.asc
Description: PGP signature