Closed laanwj closed 11 years ago
@laanwj Is this still the case? AFAIK Gavin recently fixed a RPC shutdown problem related to a NULL pointer.
Well it was an issue when I tried about a week ago. I don't think anything has changed to the RPC handling since then. You can't reproduce it?
Indeed, with server=0 it gives me an assertion in bitcoinrpc.cpp:
rpc_io_service != NULL
Caused by RPCRunLater()
call in walletpassphrase()
(in rpcwallet.cpp), because StartRPCThreads()
isn't called when fServer
is false, which inits rpc_io_service
.
@laanwj What is the best way to fix this? Check for fServer
in walletpassphrase()
? Are there more RPC commands that fail when fServer
is false?
Only walletpassphrase uses RPCRunLater at the moment. So adding a check to that command specifically will do.
At least when -server is not enabled. The following assertion fails: