Summary: | repoman segfaults | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Markus Rothe (RETIRED) <corsair> |
Component: | [OLD] Development | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED INVALID | ||
Severity: | critical | ||
Priority: | Highest | ||
Version: | 2004.3 | ||
Hardware: | PPC64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | strace-output |
Description
Markus Rothe (RETIRED)
![]() That's either a sandbox problem... Which you can just remerge portage. Or python (or a system module) is broken. FEATURES="-sandbox" emerge portage solar@simple f2c $ repoman scan # does not segfault in this dir for me with Portage 2.0.51-r15 (hardened/x86, gcc-3.3.4, glibc-2.3.4.20040808-r0, 2.4.29 i686) what does 'gdb --core=/path/to/core ; bt' say? Created attachment 49766 [details]
strace-output
"bt" gives me only this: #0 0x0000000000000000 in ?? ()
but here comes the strace-output
something bad in my environment.. repoman operates normal on ppc64 systems in this directory. (bad mix of stable and ~ packages, or something like that) Marking as INVALID closing |