Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 614372 - sys-apps/sandbox-2.10-r3 causing cc1 segmentation faults
Summary: sys-apps/sandbox-2.10-r3 causing cc1 segmentation faults
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Sandbox Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-31 18:53 UTC by Jan Ziak (atomsymbol)
Modified: 2019-03-01 04:15 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Ziak (atomsymbol) 2017-03-31 18:53:56 UTC
Hello

Context: I added the x32 ABI to the list ABIs and in consequence of this I recompiled many packages. The original ABIs were: amd64, x86.

In consequence of the recompilation, a few packages are now failing to build due to various reasons.

One reason for failures is a SIGSEGV in gcc's cc1. For example, here is the gdb backtrace for sys-libs/e2fsprogs-libs-1.43.3:

$ pwd
/var/tmp/portage/sys-libs/e2fsprogs-libs-1.43.3/work/e2fsprogs-libs-1.43.3-abi_x86_x32.x32/util

$ gdb /usr/libexec/gcc/x86_64-pc-linux-gnu/6.3.0/cc1 core.26826
Core was generated by `/usr/libexec/gcc/x86_64-pc-linux-gnu/6.3.0/cc1 -E -quiet -I . -I ../lib -I /var'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x000000382840159e in init () at dlerror.c:177
#2  _dlerror_run () at dlerror.c:129
#3  0x000000382840108e in __dlsym () at dlsym.c:70
#4  0x00007ff2eb8877d0 in get_dlsym ()
    at /var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10/libsandbox/wrappers.c:51
#5  0x00007ff2eb88669e in sb_mmap ()
    at /var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10/libsandbox/memory.c:28
#6  malloc () at /var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10/libsandbox/memory.c:50
#7  0x00007ff2eb88c7ec in __xmalloc ()
    at /var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10/libsbutil/sb_memory.c:34
#8  0x00007ff2eb884f66 in init_env_entries ()
    at /var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10/libsandbox/libsandbox.c:548
#9  sb_process_env_settings ()
    at /var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10/libsandbox/libsandbox.c:620
#10 0x00007ff2eb8840c9 in libsb_init ()
    at /var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10/libsandbox/libsandbox.c:92
#11 0x000000382740ea0b in call_init () at dl-init.c:72
#12 0x000000382740eb2c in call_init () at dl-init.c:30
#13 _dl_init () at dl-init.c:120
#14 0x0000003827400baa in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#15 ....
Comment 1 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2017-04-08 07:27:54 UTC
What are your flags on sys-apps/sandbox? Do you have abi_x86_x32 enabled there?
Comment 2 Jan Ziak (atomsymbol) 2017-04-08 10:10:42 UTC
(In reply to Michał Górny from comment #1)
> What are your flags on sys-apps/sandbox? Do you have abi_x86_x32 enabled
> there?

The enabled flags were: ABI_X86="32 64 x32"