log☇︎
447800+ entries in 0.287s
trinque: jurov: according to this you lose a lot of detail, i.e only get statistics for the line of the macro call http://codingfreak.blogspot.com/2009/02/gcov-analyzing-code-produced-with-gcc.html
jurov: can gcov cope with templated function generated by macros?
trinque: mircea_popescu: I'm sure I'm about to see a nightmare when I pull the deps into the gcov thinger
mircea_popescu: <trinque> might be able to just rip those bits off from the dep, then cut off the dep <<< ahahaha you.
mircea_popescu: alternatively, feed it the last few blocks through the mechanism discussed that alf created recently i guess.
trinque: k, ty
mircea_popescu: n ProcessMessage()\n\nProcessMessage(block, 947244 bytes) FAILED\n" which is the confirmation. then increase the number o' locks.
mircea_popescu: trinque, asciilifeform, wimc : if client fails to progress past 363736, the likely culprit is the db locks limit. look in derp.log (assuming standard derp) for "REORGANIZE\nREORGANIZE: Disconnect 6 blocks; 000000000000000006a3..000000000000000013fe\nREORGANIZE: Connect 7 blocks; 000000000000000006a3..0000000000000000014e\n\n\n************************\nEXCEPTION: 11DbException\nDb::get: Cannot allocate memory\nbitcoin i
assbot: Logged on 15-02-2015 22:34:28; asciilifeform: 2) tearing out 'boost' while keeping the project in cpp will turn it into an unreadable morass of crud that makes the existing turd look like the finest sausage
trinque: anyhow this is what I wanna see with the gcov thing
trinque: it'd be boost's interconnectedness that might prevent it, maybe
punkman: you'll just have to reimplement everything
trinque: might be able to just rip those bits off from the dep, then cut off the dep
trinque: it'll be neat to see for example how much of boost or openssl is actually used
trinque: I was surprised to find that bitcoin doesn't actually look that *big* compared to other C++ projects I've seen
trinque: speaking of which, I'm adding the coverage flag to the deps too, and will regen that gcovr html thereafter
assbot: Shout out to the American Core Devs that are spending their 4th ensuring the health of the blockchain : Bitcoin ... ( http://bit.ly/1TcE1R7 )
trinque: ass-goblins in the intertubes
mircea_popescu: asciilifeform the dispute was 730/736
trinque: with the whip iirc
shinohai: @ danielpbarron I like table-flipping Jesus best.
danielpbarron: http://log.bitcoin-assets.com/?date=04-07-2015#1186869 << it's not unlike my approach to Christianity -- most everyone already believes in the nice sounding bits, so why should I bother talking about them? I stick to the parts of the message that are not popular ☝︎
mod6: ah ok thanks
mod6: shinohai: is that with your v0.5.3.1-RELEASE node?
jurov: lol, that's actually true that dick continues deeper in the body
williamdunne: Wooo, now I get to brag about my 3 inch glory!
trinque: williamdunne: no one can tell you where your dick begins and ends... this is AMERICA!
punkman: trinque: I think that's to be expected with orphanage amputations. I have those and also plenty of "ERROR: AcceptToMemoryPool() : nonstandard transaction type"
trinque: you have to measure inflation from the balls!
fluffypony: is that a post-coital penis joke?
williamdunne: True, some things are deflationary too, dependent on how you measure 'em
trinque: well, matters how you measure inflation too
williamdunne: I'm not going to disagree with you completely, but I do still believe that S&P500 beats inflation by a couple of percent
trinque: I'm sure they used to mean something else, but we're in bizarro land where the length of a meter changes day to day
trinque: williamdunne: I tend to take stock market prices as inflation indicators these days
assbot: A Random Ass Kicking of Wall Street | Following the Trend ... ( http://bit.ly/1LKBFH4 )
asciilifeform out to meatspace for most of the remaining day
danielpbarron: https://bitcointalk.org/index.php?topic=1108304.0 >> F2Pool is building on a wrong side and there is fake confirmation since block 363731. (EDIT: the bogus chain of 363731 is already orphaned and not relevant to normal users)
danielpbarron: the one stuck at 36 is not limited to one seed, but it is running 0.5.3.1ish on a pogo with archlinux
asciilifeform: mod6: i've been synced for ~1hour and it looks like it's firmly stuck there
mod6: <+asciilifeform> has anybody as of this moment received a block past 363734 from mircea_popescu's node ? << im a day a way or so yet
mod6: <+phf> apparently gcc doesn't always include all the necessary pthread bits (not just openbsd but other unixes), which results in segfault on launch << on my obsd 5.6 on x86-64 that's the same problem i kept running into; segfault at execution time.
asciilifeform: ;;later tell mircea_popescu any of your nodes past 363734 at this time ?
mod6: <+asciilifeform> phf: you may be the first to achieve openbsd build! consider posting recipe << please do!
asciilifeform: ;;later tell kakobrekla my current understanding of the ph0rk situation is that your hypothesis re: miners being dumb as bricks is essentially correct... ☟︎☟︎☟︎
punkman: heh "I shook hands with the man I did most of the talking with and they took off... I was a little shooken up but realized I made a big mistake! I forgot to shake the black police detective's hand... shit!!! "
asciilifeform: has anybody as of this moment received a block past 363734 from mircea_popescu's node ?
asciilifeform: ;;later tell mircea_popescu i built stator on dulap just now. unchanged from public recipe other than the 'realpath' thing (mentioned earlier.) same process ought to work on your other centos boxes. it will run as a public node as soon as i shove a blockchain in there.
phf: asciilifeform: i have a small backlog of things i want to send to the list, i'll wrap it up sometime over the weekend
phf: apparently gcc doesn't always include all the necessary pthread bits (not just openbsd but other unixes), which results in segfault on launch
phf: asciilifeform: it pretty much builds out of the box. the only tricky part is the " -Wl,--whole-archive -lpthread -Wl,--no-whole-archive" business
asciilifeform: send it to the ml ?
phf: i had to make some minor changes http://paste.lisp.org/display/151074
asciilifeform: phf: you may be the first to achieve openbsd build! consider posting recipe
asciilifeform: 'nd that they sell over 30k student emails for $20, which I had bought;' << l337 sp4mz0r ?
assbot: 2 police detectives showed up to my house for cyber crime yesterday. - GoFuckYourself.com - Adult Webmaster Forum ... ( http://bit.ly/1UlYt3p )
danielpbarron: http://gfy.com/fucking-around-and-program-discussion/1169541-2-police-detectives-house-cyber-crime-yesterday-post20514733.html >> They said tax information and records were continually being pulled. They kept asking me questions about bitcoin, blah blah blah.
punkman: sig op parallelism would help in that regard
punkman: as it is 0.5.3.1/0.5.4 versions will accept blocks of version 1 and 2, allowing shitgnomes to induce forks. what's gonna happen with this? ☟︎
asciilifeform: can't think of any reason not to ☟︎
punkman: asciilifeform: what do you think about making no-verifysig-skip the default for next release?
punkman: yeah that's what I did
asciilifeform: as temporary workaround, replace the realpath thing (whole right side of equal sign) with the absolute path of 'ourlibs'
punkman: maybe we should add a .conf option that lets whoever really wants it to skip VerifySig between checkpoints ☟︎
asciilifeform: which is used in the script
asciilifeform: i did learn that many linux distros lack 'realpath' ☟︎
punkman: no-verifysig-skipping stator reached 169k, so I'm gonnna call this a success for now.
assbot: Logged on 04-07-2015 07:33:02; mircea_popescu: and that's 40 gb's worth of magic number.
asciilifeform: 363673... almost there
asciilifeform: the buggers like to monkey with versioning? fine - let's nail their ears to their heads.
asciilifeform: and from general principle, there is no reason ~not~ to make life maximally difficult for the enemy if this costs us nothing
assbot: Logged on 04-07-2015 07:21:18; mircea_popescu: but at any rate : setting the "nversion" to maxint has at least the important symbolic significance of saying "this is the last version".
cazalla: now and then i've thought of the few teacher's aids that would come for a school term as part of their studies.. they were so young and pretty but would be old bags now
shinohai: I always wanted to fuck my math teacher. She was smokin'
cazalla: tbh at 17 i think i would've been willing to do 22 years to fuck my english teacher
assbot: Teacher, accused of threesome with student, avoids jail time; posts gleeful pic to Instagram | myfox8.com ... ( http://bit.ly/1HD738B )
assbot: Florida teacher who had sex with three teens sentenced to 22 years in prison | myfox8.com ... ( http://bit.ly/1HD6N9w )
cazalla: wow GG America, well and truly lost the plot now http://myfox8.com/2015/07/03/florida-teacher-who-had-sex-with-three-teens-sentenced-to-22-years-in-prison/
assbot: New Bitcoin vulnerability: A transaction that takes at least 3 minutes to verify ... ( http://bit.ly/1HD6BHo )
punkman: https://bitcointalk.org/?topic=140078 relevant to ^
punkman: in other news, stator (with openssl1.0.1g) patched to not skip VerifySignature, has not barfed up to block 146k (previous attempt barfed earlier than that)
mircea_popescu: quantum computing will solve this.
shinohai: It appears f2p pool "almost" mined them out xD
kakobrekla: fees not large enough to offset the finite speed of light
mircea_popescu: check out all the miners that were mining off thin air, incidentally. because the bandwidth doubled so much.
kakobrekla: or does it need to work only on alpha centauri?
punkman: cpu mining code probably needs more than a couple fixes
mircea_popescu: i thought reddit went private.
mircea_popescu: honestly i fully expect fail to "happen"
kakobrekla: so if nothing else, cpu mining code needs to be updated in the ref implementation now or what
assbot: If you are using any wallet other than Bitcoin Core 0.10.x or 0.9.5 (or something backed by one of those versions), then you should not trust incoming transactions until they have ~30 confirmations. : Bitcoin ... ( http://bit.ly/1G0jGVG )
shinohai: http://redd.it/3c305f <<< whelp can't trust my 0.5.3 node /s
punkman: petertodd: "Honestly I was half-expecting this to happen, and was actually busy writing up a warning for SPV wallets users when this issue came up."
punkman: "We are using 10.2 but got this message anyway: "Your node software is out of date and may accept an invalid blockchain fork. Do not trust confirmation."" "There was a mistake made and an alert that showed up on v0.10.2 was sent out accidentally; should be now fixed."
mircea_popescu: http://xenbits.xen.org/xsa/advisory-135.html << at least they sign.
assbot: Logged on 04-07-2015 04:33:37; mod6: shinohai: is your v0.5.3.1-RELEASE node up to dayte?
shinohai: so http://log.bitcoin-assets.com//?date=04-07-2015#1186636 almost there mod6 ☝︎
shinohai: I'm at 254300 this morning, yay
assbot: Logged on 04-07-2015 04:30:43; mircea_popescu: Uh oh all these block explorers just flipped over to the invalid chain:
punkman: next one was good too http://oglaf.com/rangerron/