|
From: | Christopher Kleen |
Subject: | [Sks-devel] Problems with sks_build |
Date: | Tue, 20 Mar 2012 02:30:39 +0100 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120312 Thunderbird/11.0 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi @ *. ! I have problems while building a database using a dump. If I use the sks build utility the process always ends at the following point, the size of the DB folder is always 77MB andthe process is just stopable with the kill signal. > # /usr/sbin/sks build /var/lib/sks/dump/*.pgp -n 10 -cache 100 > === Running (fast)build... === > Loading keys...done With a greater -n flag, the process generates a segmentation fault and the size of the DB folder is 7,5 MB: > # /usr/sbin/sksbuild /var/lib/sks/dump/*.pgp-n 20 -cache 100 > Loading keys...done > Segmentation fault The fastbuild commands fails too. I tried to use two different dumps. That is not the failure. I use the SKS from the Debian repo. The version is: 1.1.1+dpkgv3-7. The system is: x86_64, 2.6.38.2 with grsec, Debian squeeze. strace provides the following output: In case of '-n 10': > brk(0x14faa000) = 0x14faa000 > brk(0x150a3000) = 0x150a3000 > brk(0x1519c000) = 0x1519c000 > mmap(NULL, 2170880, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ff862088000 > pread(5, "\0\0\0\0\1\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\1\5\0\0\0\0\0\0"..., 2048, 2048) = 2048 > brk(0x15295000) = 0x15295000 > brk(0x1538e000) = 0x1538e000 > brk(0x15487000) = 0x15487000 > brk(0x15580000) = 0x15580000 > futex(0x7ff87ad2c358, FUTEX_WAIT, 2, NULL At this point nothing happens anymore. In case of '-n 20': > brk(0x3a001000) = 0x3a001000 > brk(0x3a0fa000) = 0x3a0fa000 > brk(0x3a1f3000) = 0x3a1f3000 > --- SIGSEGV (Segmentation fault) @ 0 (0) --- > getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 > rt_sigaction(SIGSEGV, {SIG_DFL, [], SA_RESTORER, 0x7f8f3b024030}, NULL, 8) = 0 > rt_sigreturn(0xb) = 881714904 > --- SIGSEGV (Segmentation fault) @ 0 (0) --- > +++ killed by SIGSEGV +++ > Segmentation fault I have no idea to fix it. Hours of using Google were in vain. So I hope that anybody of you will have mercy with me =) Yours, Christopher - -- Christopher Kleen www.kleen.ch PGP/GPG-Schlüssel: http://gpg.kleen.ch S/MIME-Zertifikat: http://smime.kleen.ch -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iQIcBAEBAgAGBQJPZ92/AAoJEAdHe9DiVf9zdFUP/1jvDwVuu9L5kCzoR5Zphget ViSjEaPzUSIH2zerm+WRe7VDZOzK6a5YHj+/96BKVnOX33nTzQwuoXBJ8jOmux5y Stm5YlrDtbRVhaLKWkpQJKs8AjvZGK5vd3Of86xTXVhxRLrSPQwRVRU8Aoo6Q+EZ HS65vzgUVrp7mQ6FPP4YanVUvWnRImPQXKxjdEqwQftuN8fcpN/A+raXbZlWkAm9 oFNpJQTs4o7mbZdK4EwynY8OJRQYdLWOWlT8i082h1t+rubmfXFtcy3QEogy7ZVd 9zQomckSGm7DKccA2J2ALpXkAjsisPhCZVZor35Ny0l/rTmhN3aM1WTUIz7RdnoL KKQChdq37RscsZXA6BvG/ZiWOQ/Z2jok1/JmgQeosIFsTbTlzWDiWQbb9DvbtnTD qbe8XoUscqeucwiFPzZL1McXsFNum/OmrD5rdA2oSHg4sUPgligCHmLMlnwTEy6p I/eJpHB5uPpb6Z0wLJk1ZgazbTKDs5gCdHh7X45B5LGoq3etwaQPrFKwjB+QdEwx PtDO3gvBuHTqn4EVIXIvDpad6Qnyr+qty6VGm5nLgZpcwU8JJ9c4/q5nBdxclN2t KIknxg5l8e1hiqAT6fyWelHZ/VPdfQ/D4NabcBk7AilK5L6E1POc7JUA7jpAQzXe DnzLNLGLJsEnK2rzdW/R =ZzZ8 -----END PGP SIGNATURE----- |
[Prev in Thread] | Current Thread | [Next in Thread] |