12017-03-12T00:29:44  *** jtimon has joined #bitcoin-core-dev
  22017-03-12T00:45:05  *** davec has quit IRC
  32017-03-12T00:56:25  *** davec has joined #bitcoin-core-dev
  42017-03-12T01:35:32  *** CubicEarth has joined #bitcoin-core-dev
  52017-03-12T01:35:54  *** JackH has quit IRC
  62017-03-12T01:38:46  *** CubicEarth has quit IRC
  72017-03-12T01:38:59  *** CubicEarth has joined #bitcoin-core-dev
  82017-03-12T02:11:55  *** dcousens has quit IRC
  92017-03-12T02:49:51  *** AaronvanW has quit IRC
 102017-03-12T02:51:41  *** CubicEarth has quit IRC
 112017-03-12T02:54:05  *** Ylbam has quit IRC
 122017-03-12T02:55:00  *** jtimon has quit IRC
 132017-03-12T02:56:17  *** Chris_Stewart_5 has quit IRC
 142017-03-12T02:58:31  *** CubicEarth has joined #bitcoin-core-dev
 152017-03-12T03:00:00  *** CubicEarth has joined #bitcoin-core-dev
 162017-03-12T03:01:58  *** Chris_Stewart_5 has joined #bitcoin-core-dev
 172017-03-12T03:13:49  *** Victor_sueca has joined #bitcoin-core-dev
 182017-03-12T03:16:08  *** Victorsueca has quit IRC
 192017-03-12T03:23:20  *** wudayoda has quit IRC
 202017-03-12T03:30:58  *** arowser_ has joined #bitcoin-core-dev
 212017-03-12T03:31:04  *** windsok_ has joined #bitcoin-core-dev
 222017-03-12T03:31:46  *** neha__ has joined #bitcoin-core-dev
 232017-03-12T03:34:08  *** MarcoFalke_ has joined #bitcoin-core-dev
 242017-03-12T03:34:44  *** kcud_dab has joined #bitcoin-core-dev
 252017-03-12T03:35:12  *** Lightsword_ has joined #bitcoin-core-dev
 262017-03-12T03:35:20  *** Alina-malina_ has joined #bitcoin-core-dev
 272017-03-12T03:36:38  *** Alina-malina has quit IRC
 282017-03-12T03:36:39  *** nsh has quit IRC
 292017-03-12T03:36:39  *** neha has quit IRC
 302017-03-12T03:36:39  *** whphhg has quit IRC
 312017-03-12T03:36:39  *** MarcoFalke has quit IRC
 322017-03-12T03:36:40  *** cysm has quit IRC
 332017-03-12T03:36:40  *** BlueMatt has quit IRC
 342017-03-12T03:36:40  *** arowser has quit IRC
 352017-03-12T03:36:41  *** frabrunelle has quit IRC
 362017-03-12T03:36:41  *** windsok has quit IRC
 372017-03-12T03:36:41  *** slimeball has quit IRC
 382017-03-12T03:36:41  *** Lightsword has quit IRC
 392017-03-12T03:36:41  *** bad_duck has quit IRC
 402017-03-12T03:36:41  *** MarcoFalke_ is now known as MarcoFalke
 412017-03-12T03:36:52  *** Lightsword_ is now known as Lightsword
 422017-03-12T03:37:05  *** cysm- has joined #bitcoin-core-dev
 432017-03-12T03:37:51  *** BlueMatt has joined #bitcoin-core-dev
 442017-03-12T03:42:30  *** nsh- has joined #bitcoin-core-dev
 452017-03-12T03:44:28  *** whphhg has joined #bitcoin-core-dev
 462017-03-12T03:49:20  *** frabrunelle has joined #bitcoin-core-dev
 472017-03-12T03:49:21  *** CubicEarth has quit IRC
 482017-03-12T03:50:52  *** CubicEarth has joined #bitcoin-core-dev
 492017-03-12T03:51:39  *** veleiro has joined #bitcoin-core-dev
 502017-03-12T03:55:56  *** Creeper has joined #bitcoin-core-dev
 512017-03-12T04:05:23  <Chris_Stewart_5> Anyone familiar with this error? crypto/common.h:48:12: runtime error: load of misaligned address 0x7fc1ea516169 for type 'uint32_t'
 522017-03-12T04:05:33  <Chris_Stewart_5> Out of memory error possibly?
 532017-03-12T04:06:27  <gwillen> hmmm, that doesn't sound good
 542017-03-12T04:08:19  <Chris_Stewart_5> gwillen: Seems strange, all tests are passing that I am running but this seems to be happening in the setup/tear down process
 552017-03-12T04:09:09  <gwillen> what is it that you're working on that's erroring -- bitcoin-core? Or a private branch thereof?
 562017-03-12T04:09:37  <gwillen> that pointer makes me nervous, the last 3 bytes are alphabetic characters in ascii, and a pointer should never be odd
 572017-03-12T04:09:52  <gwillen> which can mean the pointer has been partly overwritten with garbage
 582017-03-12T04:10:38  <Chris_Stewart_5> it is branch on my repo, I can link if you want.
 592017-03-12T04:11:14  <Chris_Stewart_5> the gist of it is generating random permutations of datastructures and testing invariants hold true on it
 602017-03-12T04:11:59  <gwillen> feel free to link, although I suspect the problem is that you've introduced a bug somewhere in the form of overwriting memory erroneously
 612017-03-12T04:12:27  <Chris_Stewart_5> It is in #8469
 622017-03-12T04:12:29  <gribble> https://github.com/bitcoin/bitcoin/issues/8469 | [POC] Introducing property based testing to Core by Christewart · Pull Request #8469 · bitcoin/bitcoin · GitHub
 632017-03-12T04:15:02  <Chris_Stewart_5> Happening some where in between this generator: https://github.com/Christewart/bitcoin/blob/rapidcheck_mem_leak/src/test/gen/merkleblock_gen.h#L12-L30
 642017-03-12T04:15:32  <Chris_Stewart_5> and this test case: https://github.com/Christewart/bitcoin/blob/rapidcheck_mem_leak/src/test/merkleblock_properties.cpp#L26-L34
 652017-03-12T04:16:20  <gwillen> well, if the problem is a pointer being overwritten, or a use-after-free or something, the real cause of the error could be anywhere prior
 662017-03-12T04:16:29  <gwillen> this is the great sadness of debugging C code
 672017-03-12T04:16:41  <gwillen> what would be most useful in finding it, I think, would be finding what commit first introduced the problem
 682017-03-12T04:17:45  <Chris_Stewart_5> Yes, it is definitely introduced on this commit, the last commit i have on 8469 has everything working (on my machine). This pull request introduces a new dependency that we haven't set up yet :-(
 692017-03-12T04:19:34  <gwillen> Chris_Stewart_5: sorry, which commit introduces it? If it's on github, can you link directly to the specific commit? Or if it's not yet, can you push it somewhere I can see it?
 702017-03-12T04:19:56  *** wudayoda has joined #bitcoin-core-dev
 712017-03-12T04:20:04  <Chris_Stewart_5> https://github.com/Christewart/bitcoin/commit/a4052a8835f547e88c32bc6bb214b5bf108e42a7
 722017-03-12T04:20:31  <gwillen> thx, looking
 732017-03-12T04:20:39  *** dodomojo has joined #bitcoin-core-dev
 742017-03-12T04:22:37  <gmaxwell> Chris_Stewart_5: your error sounds clear enough, "load of misaligned address"   though I don't seeh how that makes sense with the code at common.h:48 on my system.
 752017-03-12T04:24:23  <Chris_Stewart_5> return be32toh(*((uint32_t*)ptr));
 762017-03-12T04:24:29  <Chris_Stewart_5> is what my line 48 is
 772017-03-12T04:24:40  <gmaxwell> okay thats not mine and that code looks potentially problmatic.
 782017-03-12T04:24:46  <gmaxwell> In C, type punning between arbritary types is not permitted. E.g. you cannot take a random character pointer, cast it to an int, and access it.  On most CPU architectures which have been invented (x86 and the more recent versions of ARM being the big obvious exceptions) it is forbidden to make a load which isn't naturally aligned, e.g. a load of a 4 byte type has to begin at a 4 byte multiple.
 792017-03-12T04:24:57  *** wudayoda has quit IRC
 802017-03-12T04:25:31  <gmaxwell> C(++) has special rules that you're allowed to access anything through a character pointer... and so you can use things like memcpy to make unaligned accesses by copying the randomly aligned pointer to a pointer of the right type (thus right alignment) elsewhere (e.g. on the stack.)
 812017-03-12T04:26:29  <gmaxwell> _My_ common.h here uses a memcpy, which would have been done specifically to avoid this problem. Are you using an old version of the code?  IIRC we fixed some issues with this not so long ago.
 822017-03-12T04:27:07  <Chris_Stewart_5> gmaxwell: Yes, I haven't rebased #8469 since I opened it IIRC
 832017-03-12T04:27:08  <gribble> https://github.com/bitcoin/bitcoin/issues/8469 | [POC] Introducing property based testing to Core by Christewart · Pull Request #8469 · bitcoin/bitcoin · GitHub
 842017-03-12T04:27:11  <gmaxwell> (Since I mentioned x86 above, even on x86 there are some instructions e.g. many of the fast SIMD loads, that require natural alignment... so you can't even just assume that since you're on x86 everything is going to be okay).
 852017-03-12T04:27:34  <gwillen> heh, I guess I was too quick to assume an unaligned load meant the pointer was the problem
 862017-03-12T04:28:45  <Chris_Stewart_5> really? You can't cast a char -> int and still access that piece of memory? Doesn't that make weak typing irrelevant then?
 872017-03-12T04:28:58  <gmaxwell> (And on older ARM systems, the CPU actually used the least significant bits of the pointer to trigger hardware byteswapping... so if you tried to read 32-bits from address 1, you'd really get a read of address 0 with the bytes swapped.. which was super duper fun to troubleshoot-- especially with all the x86 linux jockies writing alignment unsafe code, which is probably why arm dropped that rathe
 882017-03-12T04:29:04  <gmaxwell> r cool feature. :P)
 892017-03-12T04:29:35  *** wasi has joined #bitcoin-core-dev
 902017-03-12T04:31:15  <gmaxwell> Chris_Stewart_5: It's undefined behavior if the resulting pointer is not correctly aligned for its type.
 912017-03-12T04:31:33  <sipa> gmaxwell: not just alignment
 922017-03-12T04:31:54  <sipa> in C++ you just can't access any type through a type pointer that isn't compatible with it
 932017-03-12T04:32:05  *** chris200_ has joined #bitcoin-core-dev
 942017-03-12T04:32:24  <sipa> Chris_Stewart_5: you can cast an int to a char and back to int
 952017-03-12T04:32:24  <gmaxwell> sipa: I thought it was unconditionally, but googling didn't give me a cite so I said the more limited thing. :P
 962017-03-12T04:33:21  *** wudayoda has joined #bitcoin-core-dev
 972017-03-12T04:33:39  <gmaxwell> I also didn't mention, but even on x86 unaligned loads are sometimes non-trivially slower. (the main factor being if the load straddles a cache-line or page boundary, which is never the case for an aligned load)
 982017-03-12T04:33:50  <sipa> Chris_Stewart_5: and you can take a pointer to int, cast it to pointer to char, and access the data through the char pointer
 992017-03-12T04:34:01  <sipa> Chris_Stewart_5: which is a special exception that only exists for char
1002017-03-12T04:34:36  <sipa> but you can't create a char array, and then cast it to int pointer and then access it through the int pointer
1012017-03-12T04:34:48  *** chris2000 has quit IRC
1022017-03-12T04:34:56  <gmaxwell> so even if you were willing to ignore the C(++) standards and hope the compiler didn't screw you, and even if you were willing to only work on x86, and even if you were sure the result wouldn't use any alignment requiring vector loads... the result would still end up being potentially slower code. :P
1032017-03-12T04:37:04  *** grubles has quit IRC
1042017-03-12T04:38:08  *** wudayoda has quit IRC
1052017-03-12T04:40:05  <Chris_Stewart_5> So many little intracies in c/c++. Those casting semantics seem a little strange to me but I guess it is just the way it is :/
1062017-03-12T04:40:37  <gmaxwell> Funny, I like C because there are relatively few things to know!
1072017-03-12T04:42:24  <sipa> Chris_Stewart_5: it's not strange at all... you shouldn't see the program memory as an array of bytes, which you can arbitrarily treat as objects as you like
1082017-03-12T04:42:48  <sipa> Chris_Stewart_5: instead, the memory contains *objects* which have a well-defined type, and you're only allowed to access those objects through compatible pointers
1092017-03-12T04:43:11  <Chris_Stewart_5> gmaxwell: I think it boils down to 'X is easier because I learned X first! Y is waaaaay harder because I have to change the way I think' :-)
1102017-03-12T04:43:28  <gmaxwell> some of these things were more obvious in the past, objects of different kinds might get allocated out of entirely seperate chunks of memory which weren't even connected to the same hardware.
1112017-03-12T04:43:30  <sipa> note that many C/C++ codebases (and even bitcoin core before 0.14) violate that rule usually
1122017-03-12T04:44:28  <sipa> Chris_Stewart_5: these rules for example allow the C++ compiler to assume that two pointers of different type never refer to the same object, so a write through one can be known to never invalidate perhaps loaded-in-registers information from the other object
1132017-03-12T04:48:30  <gmaxwell> Chris_Stewart_5: dunno about that, the C language specification (at least for ansi C), which is more exact than even exists for most other language is very small (I think about 250 pages) compared to that of other language where their behavior is at all reproducable. (e.g. I think common lisp's spec is about 2000 pages).
1142017-03-12T04:48:40  <gmaxwell> same can't be said for C++ however.
1152017-03-12T04:50:54  <Chris_Stewart_5> gmaxwell: hah, good point. Seems like every new language has turing complete type systems these days
1162017-03-12T04:50:55  *** mol has quit IRC
1172017-03-12T04:51:03  *** moli_ has joined #bitcoin-core-dev
1182017-03-12T04:52:31  *** dodomojo_ has joined #bitcoin-core-dev
1192017-03-12T04:53:49  <gmaxwell> well it turns out that it's difficult to produce any complex non-linear system that isn't-- with some gryrantions and squinting-- turing complete. C macros are turing complete if you're willing to loop the preprocessor. :)  (doubly so because physical computers are not, pedantically, turing complete themselves due to having finite memory/storage.. and many non-turning complete langauges are equi
1202017-03-12T04:53:55  <gmaxwell> vilent to a turing machine with bounded-space/time...)
1212017-03-12T04:55:41  <Chris_Stewart_5> sipa: I didn't realize that property is preserved. I always get caught up on the whole int and char casting stuff and makes me wondering if there are *more* special cases I don't know about.
1222017-03-12T04:55:52  *** dodomojo has quit IRC
1232017-03-12T04:56:19  <Chris_Stewart_5> Any way, I suppose my misunderstanding of C/C++ are a little off topic for this channel, rebasing onto master now.
1242017-03-12T04:56:34  <Chris_Stewart_5> Hopefully the new defintion fixes my problem
1252017-03-12T05:04:30  *** CubicEarth has quit IRC
1262017-03-12T05:12:37  <Chris_Stewart_5> What is the process for getting a bigger pull request like this merged in any way? Seems like most think it is a good idea, but we need to get some sort of managed dependency set up for rapidcheck
1272017-03-12T05:13:00  <Chris_Stewart_5> It is finding stuff, which is encouraging
1282017-03-12T05:14:50  *** wudayoda has joined #bitcoin-core-dev
1292017-03-12T05:18:57  *** wudayoda has quit IRC
1302017-03-12T05:22:21  <Chris_Stewart_5> Seems like it would be a good idea to encourage this kind of testing for down stream projects such as elements too..
1312017-03-12T05:37:19  *** dodomojo has joined #bitcoin-core-dev
1322017-03-12T05:39:52  *** neha__ has quit IRC
1332017-03-12T05:40:40  *** dodomojo_ has quit IRC
1342017-03-12T05:41:35  *** tunafizz has quit IRC
1352017-03-12T05:50:49  *** veleiro has quit IRC
1362017-03-12T06:21:55  *** arubi has quit IRC
1372017-03-12T06:24:13  *** dodomojo has quit IRC
1382017-03-12T06:26:17  *** arubi has joined #bitcoin-core-dev
1392017-03-12T06:30:10  *** tunafizz has joined #bitcoin-core-dev
1402017-03-12T06:31:10  *** dodomojo has joined #bitcoin-core-dev
1412017-03-12T07:01:12  *** Victor_sueca has quit IRC
1422017-03-12T07:02:20  *** Victor_sueca has joined #bitcoin-core-dev
1432017-03-12T07:28:13  *** Chris_Stewart_5 has quit IRC
1442017-03-12T07:39:26  *** wudayoda has joined #bitcoin-core-dev
1452017-03-12T07:43:52  *** wudayoda has quit IRC
1462017-03-12T07:44:14  *** tunafizz has quit IRC
1472017-03-12T08:12:35  *** dodomojo has quit IRC
1482017-03-12T08:18:00  *** Ylbam has joined #bitcoin-core-dev
1492017-03-12T08:59:46  *** harrymm1 has joined #bitcoin-core-dev
1502017-03-12T09:01:36  *** dodomojo has joined #bitcoin-core-dev
1512017-03-12T09:02:10  *** harrymm has quit IRC
1522017-03-12T09:06:28  *** dodomojo has quit IRC
1532017-03-12T09:13:15  *** Victor_sueca has quit IRC
1542017-03-12T09:14:22  *** Victor_sueca has joined #bitcoin-core-dev
1552017-03-12T09:40:13  *** wudayoda has joined #bitcoin-core-dev
1562017-03-12T09:42:53  *** Alina-malina_ has quit IRC
1572017-03-12T09:42:53  *** Alina-malina_ has joined #bitcoin-core-dev
1582017-03-12T09:43:38  *** Alina-malina_ is now known as Alina-malina
1592017-03-12T09:44:37  *** wudayoda has quit IRC
1602017-03-12T09:48:25  *** aalex__ has joined #bitcoin-core-dev
1612017-03-12T09:56:04  *** aalex__ has quit IRC
1622017-03-12T09:56:14  *** dodomojo has joined #bitcoin-core-dev
1632017-03-12T10:00:22  *** dodomojo has quit IRC
1642017-03-12T10:28:54  *** Victor_sueca is now known as Victorsueca
1652017-03-12T11:02:45  *** jtimon has joined #bitcoin-core-dev
1662017-03-12T11:08:35  *** nemgun has joined #bitcoin-core-dev
1672017-03-12T11:09:59  *** nemgun has joined #bitcoin-core-dev
1682017-03-12T11:10:18  <nemgun> hello
1692017-03-12T11:22:39  *** thestranger has joined #bitcoin-core-dev
1702017-03-12T11:33:47  *** str4d has quit IRC
1712017-03-12T11:37:45  *** Ruben has joined #bitcoin-core-dev
1722017-03-12T11:40:12  *** Ruben has quit IRC
1732017-03-12T11:40:59  *** wudayoda has joined #bitcoin-core-dev
1742017-03-12T11:44:15  *** dodomojo has joined #bitcoin-core-dev
1752017-03-12T11:45:22  *** wudayoda has quit IRC
1762017-03-12T11:49:01  *** dodomojo has quit IRC
1772017-03-12T11:52:28  *** AaronvanW has joined #bitcoin-core-dev
1782017-03-12T11:52:29  *** AaronvanW has joined #bitcoin-core-dev
1792017-03-12T12:15:25  *** mryandao has joined #bitcoin-core-dev
1802017-03-12T12:26:27  *** jtimon has quit IRC
1812017-03-12T12:36:45  *** JackH has joined #bitcoin-core-dev
1822017-03-12T12:42:16  <bitcoin-git> [bitcoin] laanwj opened pull request #9979: p2p: Bare minimum to support UNIX sockets (master...2017_03_unix_socket_p2p) https://github.com/bitcoin/bitcoin/pull/9979
1832017-03-12T12:46:38  *** Victorsueca has quit IRC
1842017-03-12T12:47:45  *** Victorsueca has joined #bitcoin-core-dev
1852017-03-12T13:15:34  *** jouke_ has quit IRC
1862017-03-12T13:16:54  *** jouke has joined #bitcoin-core-dev
1872017-03-12T13:19:50  *** nemgun has quit IRC
1882017-03-12T13:20:18  *** nemgun has joined #bitcoin-core-dev
1892017-03-12T13:41:43  *** wudayoda has joined #bitcoin-core-dev
1902017-03-12T13:46:07  *** wudayoda has quit IRC
1912017-03-12T13:46:12  *** thestranger has quit IRC
1922017-03-12T13:52:47  *** nemgun1 has joined #bitcoin-core-dev
1932017-03-12T13:54:55  *** nemgun has quit IRC
1942017-03-12T13:56:47  *** nemgun has joined #bitcoin-core-dev
1952017-03-12T13:58:48  *** thestranger has joined #bitcoin-core-dev
1962017-03-12T13:59:27  *** nemgun1 has quit IRC
1972017-03-12T14:00:38  *** dodomojo has joined #bitcoin-core-dev
1982017-03-12T14:23:19  *** nemgun1 has joined #bitcoin-core-dev
1992017-03-12T14:23:42  *** wudayoda has joined #bitcoin-core-dev
2002017-03-12T14:26:25  *** nemgun has quit IRC
2012017-03-12T14:27:43  *** davec has quit IRC
2022017-03-12T14:29:14  *** davec has joined #bitcoin-core-dev
2032017-03-12T14:30:39  *** aalex__ has joined #bitcoin-core-dev
2042017-03-12T14:31:58  *** wudayoda has quit IRC
2052017-03-12T14:32:50  *** nemgun1 has quit IRC
2062017-03-12T14:33:16  *** nemgun1 has joined #bitcoin-core-dev
2072017-03-12T14:36:55  *** aalex__ has quit IRC
2082017-03-12T14:42:27  *** thestranger has quit IRC
2092017-03-12T14:47:20  *** wudayoda has joined #bitcoin-core-dev
2102017-03-12T14:51:57  *** wudayoda has quit IRC
2112017-03-12T14:55:21  *** nemgun has joined #bitcoin-core-dev
2122017-03-12T14:58:25  *** nemgun1 has quit IRC
2132017-03-12T15:01:04  *** nemgun1 has joined #bitcoin-core-dev
2142017-03-12T15:04:22  *** nemgun has quit IRC
2152017-03-12T15:12:40  *** Guyver2 has joined #bitcoin-core-dev
2162017-03-12T15:18:08  *** paveljanik has joined #bitcoin-core-dev
2172017-03-12T15:31:55  *** thestranger has joined #bitcoin-core-dev
2182017-03-12T15:52:01  <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/21833f9456f6...7e58b41bd7ce
2192017-03-12T15:52:02  <bitcoin-git> bitcoin/master c624753 Cory Fields: depends: fix zlib build on osx...
2202017-03-12T15:52:02  <bitcoin-git> bitcoin/master 7e58b41 Wladimir J. van der Laan: Merge #9973: depends: fix zlib build on osx...
2212017-03-12T15:52:23  <bitcoin-git> [bitcoin] laanwj closed pull request #9973: depends: fix zlib build on osx (master...fix-zlib-osx) https://github.com/bitcoin/bitcoin/pull/9973
2222017-03-12T16:00:56  *** To7 has joined #bitcoin-core-dev
2232017-03-12T16:02:07  *** Chris_Stewart_5 has joined #bitcoin-core-dev
2242017-03-12T16:07:14  *** nemgun has joined #bitcoin-core-dev
2252017-03-12T16:09:12  *** wudayoda has joined #bitcoin-core-dev
2262017-03-12T16:09:55  *** nemgun1 has quit IRC
2272017-03-12T16:13:28  *** wudayoda has quit IRC
2282017-03-12T16:14:17  *** BashCo_ has joined #bitcoin-core-dev
2292017-03-12T16:16:28  *** BashCo has quit IRC
2302017-03-12T16:27:48  *** grubles has joined #bitcoin-core-dev
2312017-03-12T16:42:42  *** eenoch is now known as eenoch_
2322017-03-12T16:44:22  *** eenoch_ is now known as eenoch
2332017-03-12T16:57:10  <bitcoin-git> [bitcoin] Christewart opened pull request #9980: Fix mem access violation merkleblock (master...fix_mem_access_violation_merkleblock) https://github.com/bitcoin/bitcoin/pull/9980
2342017-03-12T17:13:36  *** nemgun1 has joined #bitcoin-core-dev
2352017-03-12T17:16:24  *** nemgun has quit IRC
2362017-03-12T17:17:11  *** thestranger has quit IRC
2372017-03-12T17:21:38  *** wudayoda has joined #bitcoin-core-dev
2382017-03-12T17:25:57  *** wudayoda has quit IRC
2392017-03-12T17:28:23  *** eenoch is now known as eenoch_
2402017-03-12T17:33:35  *** eenoch has joined #bitcoin-core-dev
2412017-03-12T17:51:57  *** jtimon has joined #bitcoin-core-dev
2422017-03-12T17:54:46  *** nemgun has joined #bitcoin-core-dev
2432017-03-12T17:57:54  *** nemgun1 has quit IRC
2442017-03-12T18:10:56  *** wudayoda has joined #bitcoin-core-dev
2452017-03-12T18:47:48  *** CubicEarth has joined #bitcoin-core-dev
2462017-03-12T19:03:37  *** Giszmo has quit IRC
2472017-03-12T19:03:52  *** Giszmo has joined #bitcoin-core-dev
2482017-03-12T19:16:44  *** CubicEarth has quit IRC
2492017-03-12T20:05:04  *** moli_ has quit IRC
2502017-03-12T20:07:55  *** moli_ has joined #bitcoin-core-dev
2512017-03-12T20:09:20  *** moli_ has quit IRC
2522017-03-12T20:21:41  *** Creeper is now known as slimeball
2532017-03-12T20:27:35  *** nemgun1 has joined #bitcoin-core-dev
2542017-03-12T20:29:52  *** nemgun has quit IRC
2552017-03-12T20:37:45  *** nemgun1 has quit IRC
2562017-03-12T20:58:32  *** emzy has quit IRC
2572017-03-12T20:59:47  *** emzy has joined #bitcoin-core-dev
2582017-03-12T21:00:40  *** emzy has quit IRC
2592017-03-12T21:00:41  *** emzy has joined #bitcoin-core-dev
2602017-03-12T21:17:29  *** Guest45618 has joined #bitcoin-core-dev
2612017-03-12T21:23:59  *** moli_ has joined #bitcoin-core-dev
2622017-03-12T21:41:18  *** Guest45618 has quit IRC
2632017-03-12T21:47:43  *** Guyver2 has quit IRC
2642017-03-12T21:48:28  *** schmidty has joined #bitcoin-core-dev
2652017-03-12T21:54:02  *** mol has joined #bitcoin-core-dev
2662017-03-12T21:57:32  *** moli_ has quit IRC
2672017-03-12T22:33:38  *** isis has quit IRC
2682017-03-12T22:48:05  *** droark has quit IRC
2692017-03-12T22:50:13  *** laurentmt has joined #bitcoin-core-dev
2702017-03-12T22:54:24  *** JackH has quit IRC
2712017-03-12T22:54:43  *** str4d has joined #bitcoin-core-dev
2722017-03-12T23:01:37  *** wasi has quit IRC
2732017-03-12T23:01:39  *** echonaut has quit IRC
2742017-03-12T23:01:40  *** Giszmo has quit IRC
2752017-03-12T23:01:53  *** Giszmo1 has joined #bitcoin-core-dev
2762017-03-12T23:02:02  *** echonaut has joined #bitcoin-core-dev
2772017-03-12T23:02:03  *** wasi has joined #bitcoin-core-dev
2782017-03-12T23:02:24  *** molz_ has joined #bitcoin-core-dev
2792017-03-12T23:02:44  *** mol has quit IRC
2802017-03-12T23:05:02  *** laurentmt has quit IRC
2812017-03-12T23:17:52  *** justan0theruser has joined #bitcoin-core-dev
2822017-03-12T23:19:25  *** justanotheruser has quit IRC
2832017-03-12T23:34:29  *** wudayoda has quit IRC
2842017-03-12T23:34:48  *** wudayoda has joined #bitcoin-core-dev
2852017-03-12T23:35:10  *** vogelito has joined #bitcoin-core-dev
2862017-03-12T23:35:51  *** droark has joined #bitcoin-core-dev
2872017-03-12T23:47:27  *** vogelito has quit IRC
2882017-03-12T23:50:40  *** vogelito has joined #bitcoin-core-dev
2892017-03-12T23:55:05  *** vogelito has quit IRC
2902017-03-12T23:55:25  *** vogelito has joined #bitcoin-core-dev
2912017-03-12T23:59:59  *** vogelito has quit IRC