Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: segfault in 0.4.19  (Read 1930 times)

0 Members and 1 Guest are viewing this topic.

Offline puppies

segfault in 0.4.19
« on: October 02, 2014, 05:33:34 AM »

My delegate node just ran into a seg fault and I dropped a block.  Unfortunately I was not running in gdb, and the executable was stripped, so I can't get any debug info.  I am currently rebuilding to see if I can reproduce.  Has anyone else run into any problems?

* Edit by Bytemaster
   - this issue has been fixed in the latest toolkit and DAC Sun Limited has been notified that they should merge the fix and provide an update.
« Last Edit: October 02, 2014, 02:21:30 PM by bytemaster »
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline Webber

  • Sr. Member
  • ****
  • Posts: 220
    • View Profile
Re: segfault in 0.4.19
« Reply #1 on: October 02, 2014, 06:25:07 AM »
I have same issue, some other delegates have the same problem ,looks like a serious bug,only 4600 blocks now.
Bitshares2.0 witness node:delegate.webber
Bitshares2.0 API:ws://114.215.116.57:8090

Offline liondani

Re: segfault in 0.4.19
« Reply #2 on: October 02, 2014, 07:05:42 AM »
% participation dropped to 88% (red alert)
so I suggest to wait a little bit to upgrade until they give further directions (?)
  https://bitshares.OPENLEDGER.info/?r=GREECE  | You are in Control | BUY | SELL | SHORT | SWAP | LOAN | TRADE |  

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 584
    • View Profile
Re: segfault in 0.4.19
« Reply #3 on: October 02, 2014, 07:29:49 AM »
my node just crashed on 0.4.19

Code: [Select]
>>>
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 (
    [email protected]=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 (
    [email protected]=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 ([email protected]=0x5a7c2920, [email protected]=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 ([email protected]=0x5a7c2920, [email protected]=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 ([email protected]=0x7fff65ab2130) at /root/bitsharesx/libraries/fc/src/thread/task.cpp:43
#9  0x00000000006bf9d5 in fc::task_base::run ([email protected]=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 ([email protected]=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 ?? ()
>>> approve bitcoiners

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12280
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: segfault in 0.4.19
« Reply #4 on: October 02, 2014, 07:45:48 AM »
I wanted to update a price feed and it segfaulted :(
luckily it's just a 'control' node and not the delegate ... but the hardfork will happen today 19pm UTC .. :-\

- crashing on debian
- crashing on archlinux
- independent of price feed publishing ..
« Last Edit: October 02, 2014, 08:47:07 AM by xeroc »
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline Harvey

  • Sr. Member
  • ****
  • Posts: 244
    • View Profile
Re: segfault in 0.4.19
« Reply #5 on: October 02, 2014, 08:13:33 AM »
Mine crash on 0.4.19 too.
BTS       Witness:harvey-xts Seed:128.199.143.47:2015 API:wss://128.199.143.47:2016 
MUSE   Witness:harvey-xts Seed:128.199.143.47:2017 API:ws://128.199.143.47:2018

Offline emski

  • Hero Member
  • *****
  • Posts: 1283
    • View Profile
    • http://lnkd.in/nPbhxG
Re: segfault in 0.4.19
« Reply #6 on: October 02, 2014, 08:40:20 AM »
Crash Confirmed!

Offline lakerta06

Re: segfault in 0.4.19
« Reply #7 on: October 02, 2014, 08:43:24 AM »
Should we panic?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12280
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: segfault in 0.4.19
« Reply #8 on: October 02, 2014, 08:46:25 AM »
Should we panic?
na ..

delegates can still run version 0.4.18 ....
actually if the delegates were to choose not to update to 0.4.19 (which they shouldn't do currently) there will not be the hardfork at 640000:)
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline svk

Re: segfault in 0.4.19
« Reply #9 on: October 02, 2014, 09:17:43 AM »
Same here, three segfaults so far, one on the delegate machine, two on the bitsharesblocks machine..
Worker: dev.bitsharesblocks

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 584
    • View Profile
Re: segfault in 0.4.19
« Reply #10 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
>>> approve bitcoiners

Offline liondani

Re: segfault in 0.4.19
« Reply #11 on: October 02, 2014, 09:47:47 AM »
  https://bitshares.OPENLEDGER.info/?r=GREECE  | You are in Control | BUY | SELL | SHORT | SWAP | LOAN | TRADE |  

Offline serejandmyself

  • Sr. Member
  • ****
  • Posts: 358
    • View Profile
Re: segfault in 0.4.19
« Reply #12 on: October 02, 2014, 09:54:48 AM »
mine is crashing out all the time also
btsx - bitsharesrussia

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12280
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: segfault in 0.4.19
« Reply #13 on: October 02, 2014, 10:06:51 AM »
Btw .. it seems init delegates also crashed ..
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline svk

Re: segfault in 0.4.19
« Reply #14 on: October 02, 2014, 10:07:44 AM »
I've reduced my number of max connections to 10, running OK so far but monitoring it..
Worker: dev.bitsharesblocks

 

Google+