sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] [Announcement] SKS 1.1.5 Released


From: Dmitry Yu Okunev (pks.mephi.ru)
Subject: Re: [Sks-devel] [Announcement] SKS 1.1.5 Released
Date: Tue, 06 May 2014 10:21:56 +0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.4.0

Hello.

On 05/06/2014 01:46 AM, Kristian Fiskerstrand wrote:
> Hello,
> 
> We are pleased to announce the availability of a new stable SKS
> release:  Version 1.1.5.

I've compiled the new version for Debian. But:

# gdb --args sks recon
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/sks...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/sks recon
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
2014-05-06 10:19:24 Failed to listen on :::11370: Unix error: Address
family not supported by protocol - socket()
Unknown timeout type argument to DB_ENV->rep_set_timeout
DB_ENV->failchk: method not permitted before handle's open method

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000008 in ?? ()
(gdb) bt
#0  0x0000000000000008 in ?? ()
#1  0x000000000050b324 in caml_db_set_pagesize ()
#2  0x0000000000522490 in ?? ()
#3  0xfffffffff48ad493 in ?? ()
#4  0x00007ffff7fecf78 in ?? ()
#5  0x00007ffff7fecf58 in ?? ()
#6  0x00007ffff6d06de0 in ?? ()
#7  0x00007ffff6cfcdd0 in ?? ()
#8  0x0000000000441d4d in ?? ()
#9  0x000000000000001d in ?? ()
#10 0x000000000042e806 in camlReconserver__prepare_1744 ()
#11 0x00007ffff6d01180 in ?? ()
#12 0x00007ffff6d04510 in ?? ()
#13 0x00007ffff6d172a0 in ?? ()
#14 0x000000000042e839 in camlReconserver__run_1745 ()
#15 0x00007ffff6d047d0 in ?? ()
#16 0x00007ffff6d04798 in ?? ()
#17 0x00007ffff6d04530 in ?? ()
#18 0x0000000000493304 in ?? ()
#19 0x00007fffffffeaa0 in ?? ()
#20 0x00000000004931d2 in ?? ()
#21 0x0000000000000001 in ?? ()
#22 0x000000000042a7b0 in ?? ()
#23 0x00007ffff6d04458 in ?? ()
#24 0x000000000042b109 in ?? ()
#25 0x00007fffffffeaf0 in ?? ()
#26 0x000000000042b08d in ?? ()
#27 0x00007ffff6d2f308 in ?? ()
#28 0x00007ffff6d06f20 in ?? ()
#29 0x00007ffff6d07878 in ?? ()
#30 0x00007ffff6d07858 in ?? ()
#31 0x00007ffff6d0b580 in ?? ()
#32 0x0000000000428e19 in ?? ()
#33 0x00000000001c5d78 in ?? ()
#34 0x00000000005224e6 in ?? ()
#35 0x0000000000000000 in ?? ()


Is this known issue? I just don't have much time for debugging right now. :(

-- 
Best regards, Dmitry,
head of UNIX-tech department NRNU MEPhI,
tel. 8 (495) 788-56-99, add. 8255

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]