| 1 |
Hello *, |
| 2 |
|
| 3 |
For quite some time I cannot build gcl-2.6.12 on my ~amd64 box. The last |
| 4 |
successful build was on February 17 this year, the first failure on May 4. |
| 5 |
Nothing changed in gcl-2.6.12.ebuild. |
| 6 |
|
| 7 |
Now raw_gcl segfaults when called from make. When I go to |
| 8 |
/var/tmp/portage/dev-lisp/gcl-2.6.12/work/gcl/unixport/ and run raw_gcl |
| 9 |
with *exactly the same parameters* from the command line, it succeeds and |
| 10 |
produces saved_gcl. |
| 11 |
|
| 12 |
I've modified unixport/makefile to run raw_gcl under gdb and produce |
| 13 |
backtrace. This is the result: |
| 14 |
|
| 15 |
(gdb) Starting program: |
| 16 |
/var/tmp/portage/dev-lisp/gcl-2.6.12/work/gcl/unixport/raw_gcl |
| 17 |
/var/tmp/portage/dev-lisp/gcl-2.6.12/work/gcl/unixport/ -libdir |
| 18 |
/var/tmp/portage/dev-lisp/gcl-2.6.12/work/gcl/ < foo |
| 19 |
[Thread debugging using libthread_db enabled] |
| 20 |
Using host libthread_db library "/lib64/libthread_db.so.1". |
| 21 |
|
| 22 |
Program received signal SIGSEGV, Segmentation fault. |
| 23 |
0x0000000000367ee0 in calloc () |
| 24 |
(gdb) #0 0x0000000000367ee0 in calloc () |
| 25 |
#1 0x00007ffff737f687 in ?? () from /lib64/libdl.so.2 |
| 26 |
#2 0x00007ffff737f158 in dlsym () from /lib64/libdl.so.2 |
| 27 |
#3 0x00007ffff7bc2fc8 in ?? () from /usr/lib64/libsandbox.so |
| 28 |
#4 0x00007ffff7bc1e4e in ?? () from /usr/lib64/libsandbox.so |
| 29 |
#5 0x00007ffff7bc802b in ?? () from /usr/lib64/libsandbox.so |
| 30 |
#6 0x00007ffff7bc08a7 in ?? () from /usr/lib64/libsandbox.so |
| 31 |
#7 0x00007ffff7bc0c98 in ?? () from /usr/lib64/libsandbox.so |
| 32 |
#8 0x00007ffff7bc5b9c in open () from /usr/lib64/libsandbox.so |
| 33 |
#9 0x0000000000312a89 in get_phys_pages_no_malloc () |
| 34 |
#10 0x0000000000312c08 in update_real_maxpage () |
| 35 |
#11 0x0000000000365aea in gcl_init_alloc () |
| 36 |
#12 0x0000000000366ba2 in malloc () |
| 37 |
#13 0x0000000000367ed0 in calloc () |
| 38 |
#14 0x00007ffff737f687 in ?? () from /lib64/libdl.so.2 |
| 39 |
#15 0x00007ffff737f158 in dlsym () from /lib64/libdl.so.2 |
| 40 |
#16 0x00007ffff7bc2fc8 in ?? () from /usr/lib64/libsandbox.so |
| 41 |
#17 0x00007ffff7bc1e4e in ?? () from /usr/lib64/libsandbox.so |
| 42 |
#18 0x00007ffff7bc802b in ?? () from /usr/lib64/libsandbox.so |
| 43 |
#19 0x00007ffff7bc08a7 in ?? () from /usr/lib64/libsandbox.so |
| 44 |
#20 0x00007ffff7bbfa26 in ?? () from /usr/lib64/libsandbox.so |
| 45 |
#21 0x00007ffff7de82da in ?? () from /lib64/ld-linux-x86-64.so.2 |
| 46 |
#22 0x00007ffff7de83eb in ?? () from /lib64/ld-linux-x86-64.so.2 |
| 47 |
---Type <return> to continue, or q <return> to quit---Quit |
| 48 |
|
| 49 |
The problem is somehow related to the sandbox. As I said, everything was |
| 50 |
OK on February 17; I suppose sandbox has changed between this date and May |
| 51 |
4. |
| 52 |
|
| 53 |
FEATURES=-sandbox emerge gcl |
| 54 |
|
| 55 |
does not solve the problem. |
| 56 |
|
| 57 |
Any hints please? |
| 58 |
|
| 59 |
Andrey |
Archives