| Summary: | dev-vcs/git - git clone freezes when run in a sandbox | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Walther <walther.md> |
| Component: | Sandbox | Assignee: | Sandbox Maintainers <sandbox> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | robbat2 |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Walther
2012-07-07 00:10:55 UTC
what if you build sandbox with CFLAGS='-O2 -pipe' ? I recompiled sandbox using
CFLAGS="-O2 -pipe"
LDFLAGS unset
and there's no change in the result. git still stalls.
I wondered if it is related to my /var/tmp/portage being tmpfs, but mounting an external hard-drive on it didn't change the outcome, neither.
htop reports the stalled command as:
sandbox "/usr/lib/portage/bin/ebuild.sh" unpack
/bin/bash /usr/lib/portage/bin/ebuild.sh unpack
/bin/bash /usr/lib/portage/bin/ebuild.sh unpack
git clone -l -s -n /usr/portage/distfiles/egit-src/btrfs-progs.git /var/tmp/portage/sys-f
git clone -l -s -n /usr/portage/distfiles/egit-src/btrfs-progs.git /var/tmp/portage/sys-fs/btrfs-progs-0.19.11/work/btrfs-progs-0.19.11
git-upload-pack /usr/portage/distfiles/egit-src/btrfs-progs.git /var/tmp/portage/sys-fs/btrfs-progs-0.19.11/work/btrfs-progs-0.19.11
I have no idea on what other information I can provide to be of help.
please capture strace -ff of the git clone and attach it here. I haven't used strace before, so maybe I am doing this wrong. I tried this command (I had to switch to btrfs-progs-9999 because the original ebuild I used no longer uses git): strace -ff -o btrfs emerge -av1 "=sys-fs/btrfs-progs-9999" And when I do this, the sandbox command dies when trying to ptrace with an "operation not permitted" message (because it is already being traced?): >>> Emerging (1 of 1) sys-fs/btrfs-progs-9999 >>> Unpacking source... GIT update --> repository: git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git at the commit: 043a63924c9831ac52ce38f0365b9bfd628fb6a3 branch: master storage directory: "/usr/portage/distfiles/egit-src/btrfs-progs.git" checkout type: bare repository Cloning into '/var/tmp/portage/sys-fs/btrfs-progs-9999/work/btrfs-progs-9999'... ISE:_do_ptrace ptrace(PTRACE_TRACEME, ..., 0x00000000, 0x00000000): Operation not permitted /usr/lib/libsandbox.so(+0x278e)[0xf778578e] /usr/lib/libsandbox.so(+0x27fd)[0xf77857fd] /usr/lib/libsandbox.so(+0x4111)[0xf7787111] /usr/lib/libsandbox.so(+0x4c91)[0xf7787c91] /usr/lib/libsandbox.so(+0x507d)[0xf778807d] /usr/lib/libsandbox.so(execvp+0x1c8)[0xf778afc3] git[0x80db5a3] /proc/13328/cmdline: git clone -l -s -n /usr/portage/distfiles/egit-src/btrfs-progs.git /var/tmp/portage/sys-fs/btrfs-progs-9999/work/btrfs-progs-9999 fatal: The remote end hung up unexpectedly Trying to attach to an already running git-clone process doesn't give any useful information... > strace -p 13722 (git clone -l -s -n /usr/portage/distfiles/egit-src/btrfs-progs.git /var/tmp/portage/sys-fs/btrfs-progs-9999/work/btrfs-progs-9999) Process 13722 attached waitpid(13723, > strace -p 13721 (git clone -l -s -n /usr/portage/distfiles/egit-src/btrfs-progs.git /var/tmp/portage/sys-fs/btrfs-progs-9999/work/btrfs-progs-9999) Process 13721 attached read(7, Any pointers on how I should proceed? does it still happen w/current stable versions ? if so, does it fail if you do: $ sandbox $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git you're getting a ptrace error there which means you have a static binary somewhere. Nope, it's been magically fixed sometime in the last 4.5 years since I opened the bug. <_<; So yes, leave it as resolved, my GIT ain't giving any problems now. |
