This is a rare but reproducible problem. Most searches work fine but when I misspelt development below and then started the search and pressed ^C to terminate the search the following happened. Just thought I'd let the portage team know. $ emerge -s develope ^C Traceback (most recent call last): File "/usr/bin/emerge", line 13, in ? import portage File "/usr/lib/python2.2/site-packages/portage.py", line 4874, in ? settings=config() File "/usr/lib/python2.2/site-packages/portage.py", line 923, in __init__ self.regenerate() File "/usr/lib/python2.2/site-packages/portage.py", line 934, in regenerate self.configdict["auto"]["USE"]=autouse(db[root]["vartree"]) File "/usr/lib/python2.2/site-packages/portage.py", line 849, in autouse myresult=dep_check(mydep,myvartree.dbapi,use="no") File "/usr/lib/python2.2/site-packages/portage.py", line 2593, in dep_check mysplit2=dep_wordreduce(mysplit2,mydbapi,mode) File "/usr/lib/python2.2/site-packages/portage.py", line 2621, in dep_wordreduce mydep=mydbapi.match(deplist[mypos]) File "/usr/lib/python2.2/site-packages/portage.py", line 3110, in match mydep=dep_expand(origdep,self) File "/usr/lib/python2.2/site-packages/portage.py", line 2562, in dep_expand elif mydep[:1] in "=<>~!": File "/usr/lib/python2.2/site-packages/portage.py", line 239, in exithandler portageexit() NameError: global name 'portageexit' is not defined $ emerge info Portage 2.0.48-r7 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1) ================================================================= System uname: 2.6.0-test2 i686 Intel(R) Pentium(R) III Mobile CPU 1200MHz GENTOO_MIRRORS="http://ftp.gentoo.skynet.be/pub/gentoo/ http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://ftp.snt.utwente.nl/pub/os/linux/gentoo http://gentoo.linux.no/ http://trumpetti.atm.tut.fi/gentoo/ http://sunsite.cnlab-switch.ch/ftp/mirror/gentoo/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo http://darkstar.ist.utl.pt/gentoo/ http://ftp.caliu.info/pub/gentoo/ http://gentoo.inode.at/" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow avi crypt encode foomaticdb gif jpeg mad mmx mpeg ncurses pdflib png quicktime truetype xml2 xmms xv zlib directfb berkdb slang readline aalib bonobo svga java mysql X sdl gpm tcpd pam libwww ssl perl python imlib oggvorbis gtk motif opengl cdr acpi acpi4linux apache2 dvd faad fax fbcon imap kerberos maildir md5sum nptl offensive pcmcia php pnp sse tiff usb xml -apm -arts -cups -kde -libg++ -mikmod -nls -qt -spell -gtkhtml -gdbm -tcltk -guile -esd -gnome -mozilla" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -O3 -pipe" CXXFLAGS="-march=pentium3 -O3 -pipe" ACCEPT_KEYWORDS="x86 ~x86" MAKEOPTS="-j3" AUTOCLEAN="yes" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" FEATURES="sandbox ccache buildpkg"
looks like the sig handler doesn't work properly. you said this bug occures rarely. will it alway happen when you SIGKILL the emerge process? i can't reproduce it over here. Portage 2.0.48-r7 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1
It is easily reproducible. Type 'emerge -s develope' + Enter and then *immediately* press Ctrl-C. Do this successively a few times and you will see that the traceback error appears everytime. If you wait a few seconds before pressing Ctrl-C however then it kills cleanly only saying 'Killed'.
it's because python hasnt loaded the error handler soon enough ... the slower the machine the easier it would be to reproduce it ... the only thing to be done is to define the error handler asap ... even then you'd be able to kill it if you're fast enough/machine is slow enough
As explained: this can't be fixed completely
