New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix stall after resizing LMDB #1619
Conversation
…cryptonote_core/blockchain.cpp Also changed LOG_ERRORs to MERROR
If you change the L3, they should be MTRACE. They'll swamp the debug level otherwise. |
Will change and try to keep analysing |
In particular, check what LOG_PRINT_Lx get changed to. The changes you made should be noop. |
How do I use valgrind? |
Instead of running "X", you run "valgrind X". It'll be slow. |
Debug build or normal build? |
Whichever you are seeing the problems with should be fine. |
Can you tell me how to check if the changes I made were noop? |
Well... that's not super easy. If you knew how to use makefiles, you could add -E to the GCC commands and avoid linking, then you'd get preprocessed files as objects, which you could diff. Otherwise, well.. it should behave the same :) There's a chance the binaries would be the same, though those things probably contain timestamps etc so that probably doesn't help in practice. |
I think @moneromooo-monero figured out a solution by changing mutex for recursive_mutex...just testing. Closing this one in favour. |
No idea why this works, but my stall error (#1595) is fixed by changing all instances of
LOG_PRINT_L3
toMDEBUG
in/cryptonote_core/blockchain.cpp
Also took the opportunity to change
LOG_ERROR
messages toMERROR