--- Log opened Thu Sep 30 00:00:22 2021
00:10 -!- Nebraskka [~Nebraskka@user/nebraskka] has quit [Quit: Good day old chaps]
00:10 -!- Nebraskka [~Nebraskka@user/nebraskka] has joined #c-lightning
01:46 -!- ikke_sword_smith [sword_smit@bitcoinfundamentals.org] has quit [Ping timeout: 265 seconds]
01:47 -!- ikke_sword_smith [sword_smit@bitcoinfundamentals.org] has joined #c-lightning
03:08 -!- rl-d [~administr@170.51.51.215] has joined #c-lightning
03:46 < mschmoock> anyone has had this before?   "libbacktrace: unrecognized DWARF version in .debug_info at 6"
03:49 < mschmoock> my lightningd runs but fatals with these teardown errors
03:51 < mschmoock> disturbingly the issue dissapears when using VALGRIND=1 which makes it hard to discover the cause
03:53 < cdecker[m]> Sounds like a dirty build to me, `VALGRIND=1` disables some of the builtin things (such as memleak detection and backtrace) since they'd be interfering with valgrind's instrumentation, that is likely the reason for the miraculous healing there 
03:56 < mschmoock> I cleaned and rebuild everything already since I thought the same thing
03:56 < mschmoock> it must be my commit, when I remove it, pain goes way. hard to diagnose
03:58 < mschmoock> I see "gossipd: REPLY WIRE_GOSSIPD_DEV_MEMLEAK_REPLY with 0 fds" messages, can I see what that means?
03:58 < mschmoock> (this is the last log before the BROKEN teardown)
04:04 < cdecker[m]> It's a really simple message defined here https://github.com/ElementsProject/lightning/blob/b2df01dc73ea7a51ae2a495281bf4d775eafa0a4/gossipd/gossipd_wire.csv#L73-L77
04:04 < cdecker[m]> Basically "Do you have leaks?" "Yes":"no"
04:05 < cdecker[m]> But it's wired into the memleak detection which gets disabled with VALGRIND=1 so maybe that's a clue
04:05 < mschmoock> what does the "with 0 fds" mean?
04:06 < cdecker[m]> That's just because we have messages that may pass file descriptors around (gossipd connections, hsmd connections and the peer connection) but in this case it doesn't have any
04:06 < mschmoock> thx
04:07 < mschmoock> okay, will try to disable my changes one by one to circle around the memleak :D
04:08 < mschmoock> infact, I think I already located the changes that cause it
04:15 < mschmoock> ... or not
04:23 -!- rl-d_ [uid518342@id-518342.tinside.irccloud.com] has joined #c-lightning
05:23 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:29 -!- rl-d [~administr@170.51.51.215] has quit [Quit: Lost terminal]
05:29 -!- rl-d_ is now known as rl-d
06:02 -!- kenovios [~kenovios@62.74.209.161] has joined #c-lightning
06:20 -!- kenovios [~kenovios@62.74.209.161] has quit [Quit: Client closed]
08:07 -!- kexkey [~kexkey@static-198-54-132-172.cust.tzulo.com] has joined #c-lightning
10:12 -!- ikke_swo1d_smith [sword_smit@bitcoinfundamentals.org] has joined #c-lightning
10:12 -!- sturles_ [~sturles@sauron.uio.no] has joined #c-lightning
10:17 -!- Netsplit *.net <-> *.split quits: sturles, valwal, ikke_sword_smith, _niftynei, rl-d, jarthur
10:20 -!- Netsplit over, joins: valwal
10:22 -!- rl-d [uid518342@id-518342.tinside.irccloud.com] has joined #c-lightning
10:22 -!- jarthur [~jarthur@2603-8080-1540-002d-f169-568c-84c0-edb5.res6.spectrum.com] has joined #c-lightning
10:22 -!- _niftynei [~niftynei@2600:1700:d0e:284f:5481:2bed:8a23:c83] has joined #c-lightning
10:24 -!- Victorsueca [~Victorsue@user/victorsueca] has quit [Ping timeout: 265 seconds]
10:25 -!- rl-d_ [~administr@170.51.51.215] has joined #c-lightning
10:26 -!- jarthur [~jarthur@2603-8080-1540-002d-f169-568c-84c0-edb5.res6.spectrum.com] has quit [Quit: jarthur]
10:26 -!- jarthur [~jarthur@2603-8080-1540-002d-5422-0cb4-aeaf-4572.res6.spectrum.com] has joined #c-lightning
10:44 -!- _aj__ [aj@cerulean.erisian.com.au] has joined #c-lightning
10:44 -!- _aj__ [aj@cerulean.erisian.com.au] has quit [Changing host]
10:44 -!- _aj__ [aj@user/aj/x-5857768] has joined #c-lightning
10:44 -!- _aj_ [aj@user/aj/x-5857768] has quit [Ping timeout: 265 seconds]
12:06 -!- rl-d_ [~administr@170.51.51.215] has quit [Quit: Lost terminal]
12:09 -!- _aj__ is now known as _aj_
13:04 -!- mschmoock [~will@schmoock.net] has quit [Ping timeout: 252 seconds]
13:07 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Read error: Connection reset by peer]
13:08 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
13:09 -!- mschmoock [~will@schmoock.net] has joined #c-lightning
14:04 < willcl_ark> When calling `fundchannel` with `urgent` the man page claims this aims for next block.  plugins/bcli.c claims however that `urgent` is next 6 blocks target? Is this intentional?
16:15 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:20 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 252 seconds]
16:32 -!- belcher [~belcher@user/belcher] has joined #c-lightning
21:11 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
21:12 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
21:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Client Quit]
21:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
22:03 -!- jarthur [~jarthur@2603-8080-1540-002d-5422-0cb4-aeaf-4572.res6.spectrum.com] has quit [Ping timeout: 246 seconds]
22:05 -!- jarthur [~jarthur@2603-8080-1540-002d-bcfd-e74c-43c9-4dcf.res6.spectrum.com] has joined #c-lightning
23:06 -!- raj [~raj@2602:ffb6:4:e396:f816:3eff:fe47:ca2a] has joined #c-lightning
23:06 -!- nathanael_ [~nathanael@user/nathanael] has joined #c-lightning
23:07 -!- willcl_ark_ [~quassel@user/willcl-ark/x-8282106] has joined #c-lightning
23:09 -!- kexkey_ [~kexkey@static-198-54-132-172.cust.tzulo.com] has joined #c-lightning
23:14 -!- Netsplit *.net <-> *.split quits: kexkey, raj_, nathanael, willcl_ark
--- Log closed Fri Oct 01 00:00:23 2021