because again I bought a cheap coins
I think someone has transferred the coins from the left pocket to the right pocket
someone wants to cause panic .... it is clear that nobody will sell at that price
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1280. (Read 4670643 times)
November 17, 2014, 06:34:34 AM
because again I bought a cheap coins
I think someone has transferred the coins from the left pocket to the right pocket
someone wants to cause panic .... it is clear that nobody will sell at that price
November 17, 2014, 06:25:16 AM
150к sold, Now we will never see the rise! 
November 17, 2014, 06:16:59 AM
And the price continues to fall.
My outrageous LTC bids have not been hit yet. Such drama
November 17, 2014, 06:06:37 AM
And the price continues to fall.
November 17, 2014, 06:03:04 AM
Shit! Which coin is caught immediately collapses! KARMA is caught ... she fuck, now with Monero it too!
I'm going to church to light candles for the evil eye!
I'm going to church to light candles for the evil eye!
You shouldn't post using a google translator
November 17, 2014, 06:00:37 AM
November 17, 2014, 05:46:26 AM
Mega DUMP
Does that mean people expect the Bitcoin price to moon soon?
not soon rise in BTC price
November 17, 2014, 05:39:39 AM
Mega DUMP
Does that mean people expect the Bitcoin price to moon soon?
November 17, 2014, 05:09:55 AM
Shit! Which coin is caught immediately collapses! KARMA is caught ... she fuck, now with Monero it too!
I'm going to church to light candles for the evil eye!
I'm going to church to light candles for the evil eye!
November 17, 2014, 04:45:51 AM
Mega DUMP
November 17, 2014, 03:13:39 AM
why is the blockchain download 60+ days behind? it says its always up to date, but ive been syncing for the last 6 hours
Check your 'diff' command in the daemon window. If it shows the correct height (308,487 as I write this but you can check yourself on chainradar) then your download is not 60 days behind. The message you get indicates that a peer is behind, probably stuck on the wrong fork after the attack in September. Safe to ignore.
November 17, 2014, 03:01:34 AM
XMR will back to 100K or more
November 17, 2014, 02:46:14 AM
monday missives update ? November 17, 2014, 02:43:50 AM
why is the blockchain download 60+ days behind? it says its always up to date, but ive been syncing for the last 6 hours
November 17, 2014, 02:07:21 AM
monday missives update ? November 16, 2014, 09:17:49 PM
In my case it is 100% reproducible with or without debugger.
Anyone can tell how to make debug version with unstripped executables?
Anyone can tell how to make debug version with unstripped executables?
Sorry for asking stupid questions; it's
Code:
make all-debug
November 16, 2014, 09:14:10 PM
I am at block 308028. I also got the segfault, but gdb was not running.
I think it crashed in the first while loop. Now waiting for another segfault..
I think it crashed in the first while loop. Now waiting for another segfault..
Test with enabled core dumps (ulimit -c unlimited) for next time
I was running non-debug version, now I run -fsanitize=address -version, so neither gdb nor cores are needed.
In my case it is 100% reproducible with or without debugger.
Anyone can tell how to make debug version with unstripped executables?
November 16, 2014, 07:15:32 PM
I am at block 308028. I also got the segfault, but gdb was not running.
I think it crashed in the first while loop. Now waiting for another segfault..
I think it crashed in the first while loop. Now waiting for another segfault..
Test with enabled core dumps (ulimit -c unlimited) for next time
I was running non-debug version, now I run -fsanitize=address -version, so neither gdb nor cores are needed.
November 16, 2014, 06:56:14 PM
I am at block 308028. I also got the segfault, but gdb was not running.
I think it crashed in the first while loop. Now waiting for another segfault..
I think it crashed in the first while loop. Now waiting for another segfault..
Test with enabled core dumps (ulimit -c unlimited) for next time
November 16, 2014, 06:35:38 PM
Sorry, that was the stack of the wrong thread. Here is the one that's causing trouble:
Code:
(gdb) bt
#0 0x0000000000706bc4 in cryptonote::Blockchain::complete_timestamps_vector(unsigned long, std::vector >&) ()
#0 0x0000000000706bc4 in cryptonote::Blockchain::complete_timestamps_vector(unsigned long, std::vector
Remove the stray ; at src/cryptonote_core/blockchain.cpp:1059 , causes infinite loop
Thank you, otila. I have to officially declare myself blind.
Now it segfaults in Blockchain::handle_alternative_block(const block& b, const crypto::hash& id, block_verification_context& bvc).
Is anyone able to run it as a main solution? Mine can't cross block 306781.
I am at block 308028. I also got the segfault, but gdb was not running.
I think it crashed in the first while loop. Now waiting for another segfault..
Jump to: