Bug 36149 – subversion sandbox violation

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Pedro Morales 2003-12-19 19:34:13 UTC]

when emerging subversion 0.34.0 when it's about to finish installation it stops with this message:
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-subversion-0.34.0-1709.log"

link:      /dev/shm/sem.apr_autoconf
unlink:    /dev/shm/sem.XnPgU3
--------------------------------------------------------------------------------

the command just before this is:
/work/subversion-0.34.0/libtool --silent --mode=link gcc -pthread -shared  -rpath /usr/lib/svn-python/libsvn -avoid-version -module -o _wc.la svn_wc.lo -lswigpy ../../../../subversion/bindings/swig/libsvn_swig_py-1.la ../../../../subversion/libsvn_wc/libsvn_wc-1.la


Reproducible: Always
Steps to Reproduce:
1. env SVN_DUMPED=1 emerge -u subversion
2.
3.




same result, sandbox violation

[Comment 1 Pedro Morales 2003-12-19 19:35:02 UTC]

Created attachment 22456 [details]
log of sandbox violation

This is the logfile that the violation generates

[Comment 2 Pedro Morales 2003-12-21 17:23:49 UTC]

Must add that I'm not using apache2, and mie emerge --info output is:

Portage 2.0.49-r18 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20031212-r0, 2.6.0)
=================================================================
System uname: 2.6.0 i686 AMD Athlon(tm) XP 2000+
Gentoo Base System version 1.4.3.12
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://localhost/gentoo-portage"
USE="X alsa apm arts avi berkdb bonobo cdr crypt cups encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml guile imlib java jpeg kde ldap libg++ libwww mad mikmod motif mpeg mysql ncurses nls nptl oggvorbis opengl oss pam pdflib perl png postgres python qt quicktime readline sdl slang spell ssl svga tcltk tcpd tetex truetype x86 xml2 xmms xv zlib"

[Comment 3 Paul de Vrieze (RETIRED) 2003-12-23 09:55:03 UTC]

This seems to be a portage problem. /dev/shm is temporary memory that is used by newer glibc's for some kinds of interprocess communication a.o.

[Comment 4 Nicholas Jones (RETIRED) 2003-12-24 01:10:06 UTC]

You can addwrite it if you like. I'll add it in for sandbox.

[Comment 5 Pedro Morales 2003-12-26 22:41:09 UTC]

So, it's a portage's "bug"?

But the funny thing is that in a system with apache2 this does not happen.

Might it be somethin in a build without apache2 that triggers this?

Sorry for delay, been away.

[Comment 6 Paul de Vrieze (RETIRED) 2003-12-27 04:31:19 UTC]

without apache2 the package has its own included libapr/libapu and the error happens in that part. It is however a problem that is caused by the sandbox which is just triggered by the compilation.

This bug should be fixed with the newer (pre) portage versions. The most easy way to circumvent is to build with
FEATURES="-sandbox" emerge subversion