Summary: | Portage search traceback error | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Narada Sage <narada.sage> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Narada Sage
2003-08-07 08:04:46 UTC
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 |