making manifest of one of sys-kernel ebuilds going to segfault: ebuild iwlwifi-sources-9999.ebuild manifest Segmetation fault Omploaded 'iwlwifi-sources-9999.ebuild' to http://omploader.org/vNGF4ZA strace ebuild iwlwifi-sources-9999.ebuild manifest &> trace Omploaded 'trace' to http://omploader.org/vNGF4dQ eix-update, when have this ebuild in overlays failing too, of course Reproducible: Always Steps to Reproduce: ebuild iwlwifi-sources-9999.ebuild manifest Actual Results: Segmetation fault Expected Results: manifest
I can't reach that website you uploaded the ebuild and 'trace' to. Please attach them to this bug report and reopen the bug.
Created attachment 229641 [details] ebuild
Created attachment 229643 [details] strace ebuild zen-sources-9999.ebuild manifest &> trace
added with another ebuild - zen-sources this time
Created attachment 229711 [details] another trace of ebuild - other mashine
Please, paste your emerge --info output to let us see what portage version you have. @dev-portage: didn't know what to do with this bug, don't know if it has anything to do with you, sorry if it hasn't
Try rebuilding python. If that doesn't help then please post emerge --info.
(In reply to comment #3) > Created an attachment (id=229643) [details] > strace ebuild zen-sources-9999.ebuild manifest &> trace Actually I don't think it's python because the log shows this: read(10, Sandboxed process killed by signal: Segmentation fault "", 8192) Maybe it was bash. If you look at `dmesg | tail` then it should say the name of the process that segfaulted.
