Summary: | emerge --metadata and emerge --sync causes portage to segfault | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Juha Heljoranta <juha.heljoranta> |
Component: | Core | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | patrick |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Juha Heljoranta
2005-09-18 23:22:43 UTC
kernel bug? http://bugzilla.kernel.org/show_bug.cgi?id=4851 looks similar It does look similar. <snippet> Problem Description: User space application (mostly gcc, g++, collect, sed and grep) randomly segfault and cause protection errors. This goes away when I revert the randomisation-top-of-stack-randomization patch or when I run the following command: echo 0 > /proc/sys/kernel/randomize_va_space </snippet> Juha, can you try that workaround and see if that does it for you? *** This bug has been marked as a duplicate of 104151 *** I just saw a new segfault.
>>> Updating Portage cache: 64%Segmentation fault
Sep 22 09:00:24 sng emerge[15744]: segfault at 00000000000000a1 rip
00002aaaaac81608 rsp 00007fffffff8ea0 error 4
# cat /proc/sys/kernel/randomize_va_space
0
Disabling randomization helped alot but it seems that this can still occur.
Should be reopened or should I wait for next kernel update?
|