106
General Discussion / Re: segfault in 0.4.19
« on: October 02, 2014, 09:20:13 am »
0.4.19 is not safe to run. It keeps crashing. I am switching back to 0.4.18
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
>>>
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff87fff700 (LWP 4915)]
std::_Hashtable<bts::net::item_id, bts::net::item_id, std::allocator<bts::net::item_id>, std::__detail::_Identity, std::equal_to<bts::net::item_id>, std::hash<bts::net::item_id>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<true, true, true> >::find (
this=this@entry=0x45944, __k=...) at /usr/include/c++/4.8/bits/hashtable.h:1024
1024 std::size_t __n = _M_bucket_index(__k, __code);
(gdb) bt
#0 std::_Hashtable<bts::net::item_id, bts::net::item_id, std::allocator<bts::net::item_id>, std::__detail::_Identity, std::equal_to<bts::net::item_id>, std::hash<bts::net::item_id>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<true, true, true> >::find (
this=this@entry=0x45944, __k=...) at /usr/include/c++/4.8/bits/hashtable.h:1024
#1 0x0000000000a4ede5 in find (__x=..., this=0x45944) at /usr/include/c++/4.8/bits/unordered_set.h:517
#2 bts::net::detail::node_impl::process_block_during_normal_operation (this=this@entry=0x5a7c2920, originating_peer=originating_peer@entry=0x7fff659dd210,
block_message_to_process=..., message_hash=...) at /root/bitsharesx/libraries/net/node.cpp:2828
#3 0x0000000000a5068b in bts::net::detail::node_impl::process_block_message (this=this@entry=0x5a7c2920, originating_peer=originating_peer@entry=0x7fff659dd210,
message_to_process=..., message_hash=...) at /root/bitsharesx/libraries/net/node.cpp:2880
#4 0x0000000000a51d03 in bts::net::detail::node_impl::on_message (this=0x5a7c2920, originating_peer=0x7fff659dd210, received_message=...)
at /root/bitsharesx/libraries/net/node.cpp:1598
#5 0x0000000000ac034a in bts::net::detail::message_oriented_connection_impl::read_loop (this=0x7fff65a19490) at /root/bitsharesx/libraries/net/message_oriented_connection.cpp:157
#6 0x0000000000ac271c in operator() (__closure=<optimized out>) at /root/bitsharesx/libraries/net/message_oriented_connection.cpp:100
#7 fc::detail::void_functor_run<bts::net::detail::message_oriented_connection_impl::accept()::__lambda0>::run(void *, void *) (functor=<optimized out>, prom=0x7fff65ab2120)
at /root/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#8 0x00000000006bf323 in fc::task_base::run_impl (this=this@entry=0x7fff65ab2130) at /root/bitsharesx/libraries/fc/src/thread/task.cpp:43
#9 0x00000000006bf9d5 in fc::task_base::run (this=this@entry=0x7fff65ab2130) at /root/bitsharesx/libraries/fc/src/thread/task.cpp:32
#10 0x00000000006bd95b in run_next_task (this=0x7fff7c0008c0) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:415
#11 fc::thread_d::process_tasks (this=this@entry=0x7fff7c0008c0) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:439
#12 0x00000000006bdbe6 in fc::thread_d::start_process_tasks (my=140735273765056) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:395
#13 0x0000000000f4628e in make_fcontext ()
#14 0x00007fff7c0008c0 in ?? ()
#15 0x00007fff7c068be0 in ?? ()
#16 0x0000000000000000 in ?? ()
default (unlocked) >>> get_info
6 key_not_found_exception: Key Not Found
{"key":6}
th_a cached_level_map.hpp:68 fetch
{"key":6}
th_a cached_level_map.hpp:69 fetch
{"property_id":"confirmation_requirement"}
th_a chain_database.cpp:2149 get_property
{}
th_a common_api_client.cpp:2259 get_info
{"command":"get_info"}
th_a cli.cpp:556 execute_command
default (unlocked) >>> about
{
"blockchain_name": "BitShares X",
"blockchain_description": "Decentralized Autonomous Exchange",
"client_version": "v0.4.19-RC1-20-gc844ba8",
"bitshares_toolkit_revision": "c844ba8b02fb9952e32b0e2cb2378b2180cf1703",
"bitshares_toolkit_revision_age": "26 minutes ago",
"fc_revision": "c4e814d7ded6099dc4297aa843d4be7afa98b3ed",
"fc_revision_age": "32 hours ago",
"compile_date": "compiled on Oct 1 2014 at 15:22:28",
"boost_version": "1.55",
"openssl_version": "OpenSSL 1.0.1f 6 Jan 2014",
"build": "linux 64-bit"
}
default (unlocked) >>> debug_list_errors
10 assert_exception: Assert Exception
is_open(): Database is not open!
{}
th_a level_map.hpp:152 begin
error seeking to first
{}
th_a level_map.hpp:171 begin
{}
th_a common_api_client.cpp:2819 debug_list_errors
{"command":"debug_list_errors"}
th_a cli.cpp:556 execute_command
>>> about
{
"blockchain_name": "BitShares XTS",
"blockchain_description": "BitShares X Test Network",
"client_version": "dryrun-18-16-ga44e378-testnet-32",
"bitshares_toolkit_revision": "a44e378203a0d55bbd80abf28200b3b83d8e7bfd",
"bitshares_toolkit_revision_age": "17 hours ago",
"fc_revision": "c4e814d7ded6099dc4297aa843d4be7afa98b3ed",
"fc_revision_age": "24 hours ago",
"compile_date": "compiled on Sep 30 2014 at 15:05:48",
"boost_version": "1.55",
"openssl_version": "OpenSSL 1.0.1f 6 Jan 2014",
"build": "linux 64-bit"
}
>>> wallet_account_transaction_history
TIMESTAMP BLOCK FROM TO AMOUNT MEMO BALANCE FEE ID
==============================================================================================================================================================================================
2014-09-30T00:00:00 0 GENESIS tester 499,934.79111 XTS claim 1HddTkBSaxVnRL2XPpgFMVChj8BSWWC5mN 499,934.79111 XTS 0.00000 XTS [c35487]
2014-10-01T14:22:24 PENDING tester tester 0.00000 XTS register tester as a delegate N/A 0.75755 XTS 0206e8f0
2014-10-01T14:25:51 PENDING tester ASK-f50b8581 30.32150 XTS sell XTS @ 0.03297989875171083 USD / XTS N/A 0.50000 XTS 5883bf57
где можно посмотреть изменение курса bitUSD/BTSX. Хотелось бы увидеть график с момента начала торгов
There is a thread already discussing this .. search for "huge market" and author: xeroc
Wouldn't you need to be tightly integrated with an exchange on the backend to offer this? You'd need to find someone willing to trade BTC for bitBTC.
I'm pretty sure this would require at least an escrow/trusted 3rd party, because you're talking about trading across different blockchains.
You can authenticate to a BTSX name already (login feature). You're just asking to have URL lookup + auth as one step. This sort of stuff is the purpose of KeyID+DNS though. I don't want to give people even more of a reason to complain about names being non-transferrable.
there are no downvotes, only net votes, the negative ones you're seeing are simply votes for someone being removed cause they were unapproved.