Main Menu

0.4.21 segmentation fault

Started by toast, October 23, 2014, 03:23:43 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

speedy

Just want to say Thank You to whoever fixed the market font colors in v0.4.21 - I can now read the numbers :)

vikram


arubi

Quote from: xeroc on October 23, 2014, 03:45:44 PM
Quote from: arubi on October 23, 2014, 03:36:59 PM
xeroc, what are you using there? what's the version of boost? which compiler and version?
My issue was fixed in
https://github.com/BitShares/bitshares_toolkit/issues/864

can't help with yours though .. as I am not using the GUI much :(

Me neither, but it's nice to have it working. I'll wait for an eventual fix then...

Quote from: toast on October 23, 2014, 03:46:09 PM

Download from trusted server instead of p2p network.

I don't like this feature.. glad that the fix is to turn it off.


Thanks all!

toast

Quote from: arubi on October 23, 2014, 03:44:50 PM
Quote from: toast on October 23, 2014, 03:43:24 PM
The fix was to turn off chain downloader.

Ah I guess I missed that..
What's the purpose of "chain downloader"? (aside from the obvious ;) )

Download from trusted server instead of p2p network.
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

xeroc

Quote from: arubi on October 23, 2014, 03:36:59 PM
xeroc, what are you using there? what's the version of boost? which compiler and version?
My issue was fixed in
https://github.com/BitShares/bitshares_toolkit/issues/864

can't help with yours though .. as I am not using the GUI much :(

arubi

Quote from: toast on October 23, 2014, 03:43:24 PM
The fix was to turn off chain downloader.

Ah I guess I missed that..
What's the purpose of "chain downloader"? (aside from the obvious ;) )

toast

The fix was to turn off chain downloader.
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

arubi

Quote from: xeroc on October 23, 2014, 01:57:15 PM
Quote from: bytemaster on October 23, 2014, 01:48:03 PM
Quote from: xeroc on October 23, 2014, 09:31:41 AM
What sense does it make to have a RC if you won't give people the time to install and report bugs?
https://github.com/BitShares/bitshares_toolkit/issues/864

We had people file and report bugs internally.
That would be a good approach if you had all different architectures available to test with .. have you?

I just finished building on ubuntu server 14.04.1 32bit.
The cli client seems to be working well but the web wallet is not.

I keep getting redirected to http://localhost:9989/#/createwallet and even after manually navigating to http://localhost:9989/#/unlockwallet and supplying the password, I'm still being redirected back to the /createwallet page.

My wallet's name is not default, if it matters.


I'm gonna try building on sid 64bit soon. xeroc, what are you using there? what's the version of boost? which compiler and version?
Thanks.

xeroc

Quote from: bytemaster on October 23, 2014, 01:48:03 PM
Quote from: xeroc on October 23, 2014, 09:31:41 AM
What sense does it make to have a RC if you won't give people the time to install and report bugs?
https://github.com/BitShares/bitshares_toolkit/issues/864

We had people file and report bugs internally.
That would be a good approach if you had all different architectures available to test with .. have you?

bytemaster

Disable Chain Downloader by removing it from your config file.... if in doubt you can delete your config file entirely.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

bytemaster

Quote from: xeroc on October 23, 2014, 09:31:41 AM
What sense does it make to have a RC if you won't give people the time to install and report bugs?
https://github.com/BitShares/bitshares_toolkit/issues/864

We had people file and report bugs internally. 
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

GaltReport

#12
Quote from: xeroc on October 23, 2014, 09:31:41 AM
What sense does it make to have a RC if you won't give people the time to install and report bugs?
https://github.com/BitShares/bitshares_toolkit/issues/864

Good point. No sooner did I get RC1 installed and their is another release.

BTW, RC1 running fine for me.  I did find that a reboot after install again gave me a lot more memory so i do this now as regular practice.

xeroc

Quote from: emski on October 23, 2014, 10:03:09 AM
I haven't seen that issue on ubuntu 14.04 .
For me it seems to be Debian sid related ..

I need sid because of boost .. kind of sucks .. gonna install ubuntu next time :) .. or archlinux

emski

I haven't seen that issue on ubuntu 14.04 .
[url="https://bitsharestalk.org/index.php/topic,9857.0.html"]https://bitsharestalk.org/index.php/topic,9857.0.html[/url]

xeroc

What sense does it make to have a RC if you won't give people the time to install and report bugs?
https://github.com/BitShares/bitshares_toolkit/issues/864

cube

Quote from: tonyk on October 23, 2014, 03:31:04 AM
Now, we were talking about better PR (or is this the better PR? hm?)

I thought toast got some more efficient means of communication with vikram and BM than posting here  :)

I think posting technical stuff here is good.  Other people who are facing similar problems can get a quick answer.  Just like a public listed company would halt the trading of their company shares before announcing any major company movement which are share price sensitive, we do need more care when it comes to any announcement/proposal/posts that would potentially affect prices.  Having good PR would help.
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

xeroc

I am having the same segfault .. Posted at github..


2x Debian sid .. both crash
2x archlinux ... all fine

alt

post here maybe not bad,
we got chance to  join  them  :)

tonyk

#5
Now, we were talking about better PR (or is this the better PR? hm?)

I thought toast got some more efficient means of communication with vikram and BM than posting here  :)
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

bytemaster

Ok.  I'll try to reproduce.   OS?
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

toast

Quote from: bytemaster on October 23, 2014, 03:27:47 AM
Details?

I run the client and it instantly crashes with the above backtrace. What else would help?
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

bytemaster

For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

toast

vikram help!

(wallet closed) >>>
Program received signal SIGSEGV, Segmentation fault.
fc::exception::code (this=0x0) at /root/bitsharesx/libraries/fc/src/exception.cpp:105
105        int64_t      exception::code()const throw() { return my->_code;         }
(gdb) bt
#0  fc::exception::code (this=0x0) at /root/bitsharesx/libraries/fc/src/exception.cpp:105
#1  0x0000000000847419 in operator() (e=..., __closure=0x4c6d268) at /root/bitsharesx/libraries/client/client.cpp:2766
#2  fc::detail::completion_handler_impl<bts::client::client::start_networking(std::function<void()>)::__lambda13, void>::on_complete(const void *, const fc::exception_ptr &) (this=0x4c6d260, v=<optimized out>, e=...) at /root/bitsharesx/libraries/fc/include/fc/thread/future.hpp:54
#3  0x00000000008e0516 in fc::promise_base::_set_value (this=0x4c6d9d8, s=s@entry=0x0) at /root/bitsharesx/libraries/fc/src/thread/future.cpp:122
#4  0x0000000000ccfc69 in set_value (this=0x4c6d940) at /root/bitsharesx/libraries/fc/include/fc/thread/future.hpp:158
#5  fc::detail::void_functor_run<bts::net::chain_downloader::get_all_blocks(std::function<void(const bts::blockchain::full_block&, unsigned int)>, uint32_t)::__lambda1>::run(void *, void *) (functor=0x4c6d948, prom=0x4c6d940) at /root/bitsharesx/libraries/fc/include/fc/thread/task.hpp:84
#6  0x00000000008e0fd3 in fc::task_base::run_impl (this=this@entry=0x4c6d978) at /root/bitsharesx/libraries/fc/src/thread/task.cpp:43
#7  0x00000000008e1685 in fc::task_base::run (this=this@entry=0x4c6d978) at /root/bitsharesx/libraries/fc/src/thread/task.cpp:32
#8  0x00000000008df52e in run_next_task (this=0x1a0de10) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:498
#9  fc::thread_d::process_tasks (this=this@entry=0x1a0de10) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:547
#10 0x00000000008df7b6 in fc::thread_d::start_process_tasks (my=27319824) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:475
#11 0x000000000120127e in make_fcontext ()
#12 0x0000000001a0de10 in ?? ()
#13 0x0000000004c8cf00 in ?? ()
#14 0x0000000000000000 in ?? ()
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.