brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 265 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 265 seconds]
BlueMatt has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
jarthur_ has joined #bitcoin-core-dev
jarthur has quit [Ping timeout: 240 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 246 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 265 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 265 seconds]
Guest28 has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
brunoerg has joined #bitcoin-core-dev
cm has quit [Ping timeout: 246 seconds]
cm has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 264 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 246 seconds]
test__ has joined #bitcoin-core-dev
Guest28 has quit [Quit: Client closed]
brunoerg has joined #bitcoin-core-dev
flooded has quit [Ping timeout: 268 seconds]
brunoerg has quit [Ping timeout: 240 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
brunoerg has joined #bitcoin-core-dev
cmirror has quit [Remote host closed the connection]
cmirror has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 265 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 256 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 264 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
Guest54 has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
brunoerg has joined #bitcoin-core-dev
EleYah has quit [Quit: EleYah]
brunoerg has quit [Ping timeout: 250 seconds]
brunoerg has joined #bitcoin-core-dev
puchka has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 265 seconds]
Guest54 has quit [Ping timeout: 245 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 268 seconds]
Guyver2 has joined #bitcoin-core-dev
ghost43_ has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
flooded has joined #bitcoin-core-dev
<kouloumos>
Part of #18963 involved moving `BlockChecked` to a background thread; afaiu there were no objections for this particular change in that series of PRs, although there wasn't much review interest
Guyver2 has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
vysn has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 250 seconds]
<josie>
question for the gdb gurus: I'm starting and loading bitcoind with the following commands: $ gdb; file src/bitcoind; b <insert breakpoint>; run -signet
<josie>
each time I do this, the node does IBD, which is pretty annoying when debugging
aielima has joined #bitcoin-core-dev
<josie>
is this normal? or is there something about how I am starting bitcoind which is causing this?
evri has joined #bitcoin-core-dev
<kouloumos>
and it does that on startup even after you already completed IBD on signet on a previous session?
<josie>
kouloumos: yep
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 264 seconds]
<vasild>
josie: that should be the same as running "src/bitcoind -signet" without gdb
<vasild>
does it behave differently if you run "src/bitcoind -signet" compared to inside gdb?
<vasild>
gdb --args src/bitcoind -signet; b <insert breakpoint>; run <-- this will do the same but is a bit more convenient if you use it repeatedly
<vasild>
no need to exit gdb to restart from the beginning, just execute "run" again, this way the breakpoints and the arguments (-signet) will remain set
<josie>
vasild: running with gdb --args <etc> also goes through IDB every time I start it
<kouloumos>
I cannot reproduce your issue. But in general, I find attaching to the process more convenient. Because gdb allows for programmability through python, I wrote a helper that waits for the pid to start and then attaches on it. You can find it as part of this script: https://github.com/kouloumos/bitcoin/commit/0b468517f316590a0502827c4ae989ce948433cf . The script is doing more things, but for the general case you just need
<kouloumos>
to do `gdb src/bitcoind; source extend_gdb.py; b <insert breakpoint>; attach_bitcoind` and then start your bitcoind process.
<josie>
kouloumos: thanks, I'll give this a try
<josie>
vasild: interestingly, executing "run" in gdb multiple times also causes it to go through IBD every time
<vasild>
josie: yes, because it restarts the process from the beginning (like it kills/terminates any existent process and starts a new one)
<vasild>
but does it do the same if you start "src/bitcoind -signet" witout gdb?
<vasild>
do you have ~/.gdbinit? maybe that does some extra stuff?
<vasild>
is the breakpoint hit before it goes in IBD? could it be timing related?
aielima has quit [Quit: Ciao]
<vasild>
if no more clues, I would find where in the code it decides to go IBD or not and add poor-man's printout "entering IBD because variable x equals 5", "not entering IBD because x equals ..." and run inside and outside gdb and see what gets printed
<josie>
vasild: don't have a gdbinit , and no, the breakpoint is after IBD finishes. I don't think its an issue with bitcoin core, since it runs fine outside of gdb, so I'm guessing it has something to do with permissions or gdb not being able to read the blk files?
b_101 has quit [Ping timeout: 240 seconds]
brunoerg has joined #bitcoin-core-dev
b_101 has joined #bitcoin-core-dev
<josie>
anywho, thanks for the help. was hoping it was a simple thing like missing a gdb parameter, but looks like something is broken on my end. will spend some more time debugging the debugger after I finish debugging the actual thing lol
brunoerg has quit [Ping timeout: 265 seconds]
Cory has quit [Ping timeout: 265 seconds]
Cory has joined #bitcoin-core-dev
<fanquake>
To github.com:bitcoin-core/bitcoin-detached-sigs.git
<fanquake>
* [new tag] v23.2 -> v23.2
<fanquake>
To github.com:bitcoin-core/bitcoin-detached-sigs.git
<fanquake>
* [new tag] v24.1 -> v24.1
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 248 seconds]
<vasild>
josie: no idea then :( "prog -foo" should execute prog in the same way as "gdb --args prog -foo"
<willcl_ark>
Is there a reason the `guix-clean` script doesn't clean up the "guix-build-25.0rc2/output" directory?
<willcl_ark>
It's set as a precious_dir, but I'm not sure why we wouldn't clean that out. It was confusing me why `guix-attest` was outputting "all.SHA256SUMS" after I had run `guix-clean` and not yet codesigned...
<bitcoin-git>
[bitcoin] hebasto opened pull request #27684: Avoid lock order inversion in `Chainstate::ConnectTip` function (master...230516-punish) https://github.com/bitcoin/bitcoin/pull/27684
AaronvanW has joined #bitcoin-core-dev
AaronvanW has quit [Read error: Connection reset by peer]
AaronvanW has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
AaronvanW has quit [Read error: Connection reset by peer]
AaronvanW has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 264 seconds]
AaronvanW has quit [Read error: Connection reset by peer]
AaronvanW has joined #bitcoin-core-dev
AaronvanW has quit [Remote host closed the connection]
<fjahr>
josie: did you check if it's using the right datadir?
AaronvanW has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
<josie>
fjahr: yeah, I think I figured it out: the issue I was troubleshooting was somehow corrupting the chainstate/blk files when triggered. I tested this by triggering the error in gdb, exiting, and then restarting the node and confirming that it went into IBD again. restarting the node with -reindex and then running in gdb worked (e.g did not do IBD again)
brunoerg has joined #bitcoin-core-dev
<fanquake>
Why is the MSVC build still failing in new PRs
<bitcoin-git>
bitcoin/master a09269a fanquake: guix: document when certain guix patches can be dropped
<bitcoin-git>
bitcoin/master 594f05d fanquake: Merge bitcoin/bitcoin#27668: guix: document when certain patches can be dr...
<bitcoin-git>
[bitcoin] fanquake merged pull request #27668: guix: document when certain patches can be dropped (master...guix_patch_doc) https://github.com/bitcoin/bitcoin/pull/27668
<bitcoin-git>
[bitcoin] fanquake opened pull request #27688: doc: remove Security section from build-unix.md (master...build_unix_drop_security) https://github.com/bitcoin/bitcoin/pull/27688
nanotube has quit [Ping timeout: 268 seconds]
<stickies-v>
could someone please grant https://github.com/ismaelsadeeq write access to the bitcoin-dev wiki please? he's working on the v25RC (or final, if already released at that point) testing guide and will be ready to add it soon
<fanquake>
stickies-v: invited
<stickies-v>
ty
<bitcoin-git>
[bitcoin] fanquake opened pull request #27689: doc: remove mention of glibc 2.10+ (master...remove_glibc_vesion_malloc_info) https://github.com/bitcoin/bitcoin/pull/27689