andrewtoth_ has quit [Remote host closed the connection]
andrewtoth_ has joined #bitcoin-core-dev
andrewtoth_ has quit [Remote host closed the connection]
andrewtoth_ has joined #bitcoin-core-dev
greypw1495085720 has quit [Remote host closed the connection]
<bitcoin-git>
[gui-qml] hebasto merged pull request #897: qml: Do not let Qt parse the process command line (qt6...test/uri-argument-injection) https://github.com/bitcoin-core/gui-qml/pull/897
andrewtoth_ has quit [Remote host closed the connection]
andrewtoth_ has joined #bitcoin-core-dev
BGL has joined #bitcoin-core-dev
andrewtoth_ has quit [Remote host closed the connection]
andrewtoth_ has joined #bitcoin-core-dev
andrewtoth_ has quit [Remote host closed the connection]
cotsuka has quit [Read error: Connection reset by peer]
cotsuka has quit [Read error: Connection reset by peer]
eugenesiegel has joined #bitcoin-core-dev
cotsuka has joined #bitcoin-core-dev
andrewtoth_ has joined #bitcoin-core-dev
<eugenesiegel>
pinheadmz: have you run fuzzamoto with http-server lately? I ran it yesterday and hit a few hangs, but didn't have time to investigate
<pinheadmz>
been running it pretty much non stop for months, updating the branch as PRs got merged, same results. indicates some "hangs" but no crashes
<pinheadmz>
I also run it with the HTTP dict, so its more likely to compose a valid request
<pinheadmz>
same with regular bitcoin core libfuzzer, running 24/7 with a dict
<pinheadmz>
not sure what to do about the hangs, i guess i should look at those artifacts but theres a lot on my machine now and im not sure what qualifies as a hang
<eugenesiegel>
I think it's the timeout being hit
<pinheadmz>
do you know what that value is?
<pinheadmz>
fuzzamoto is also complaining its exec time is (slow!) between 50-70/sec. Im running 8 threads on 8-core machine
<eugenesiegel>
no, I think it's a few seconds. are you using the AFL_Runner `aflr` ?
<eugenesiegel>
you should be able to increase the timeout with aflr --config config.toml, and in the .toml then you can set a timeout, not sure if it will help. I can check after I'm done using the machine for other things
<pinheadmz>
what constitutes a "hang"? There's honest cases where the server just waits for more data from the client for example
<eugenesiegel>
I think it's just any input that doesn't finish processing completely after N seconds
<pinheadmz>
ok i need to look at the target code then. the server is supposed to throttle if the client doesnt read its responses
<eugenesiegel>
btw, is the machine 8 physical cores or 4 physical cores? i've noticed sometimes that using all virtual cores can not help at a certain point, probably depends on the machine