Another thing to take care of could be max tip age: if your last block time (from previous day) is more than 24h old, your node won’t leave initial block download mode and will appear as sync is not finished although all blocks are downloaded from disk. It’s a common case in regtest since blocks are not mined on a regular basis yet on demand. What you can do to fight this is to extend default age by maxtipage option set (either via command line or conf) to some greater number of seconds than 1 full day has. (e.g. maxtipage=432000 in conf for 5 days)
Hi,
I was trying to debug the zcash via gdb by adding -g flag( highlighted via red color) in the makefile. How can i do so …
below are things which i tried:
cli: zcash-cli
2503 libbitcoin_cli_a_CPPFLAGS = (AM_CPPFLAGS) (BITCOIN_INCLUDES)
2504 libbitcoin_cli_a_CXXFLAGS = (AM_CXXFLAGS) (PIE_FLAGS) -g
2505 libbitcoin_cli_a_SOURCES =
2506 rpc/client.cpp
2507 (BITCOIN_CORE_H) \
2508 (LIBZCASH_H)
2509
2510 nodist_libbitcoin_util_a_SOURCES = $(srcdir)/obj/build.h
2511 #
Also i tried this :
Start the zcash server:
src/zcashd -regtest -daemon -datadir=/home/vinni/avineeth/Zcash_work/zcash/vinni/
Run the zcash cli in GDB
gdb ./zcash-cli
r -rpcuser=avinni619 -rpcpassword=avinni619 -datadir=/home/vinni/avineeth/Zcash_work/zcash/vinni/ listaddressgroupings
r -rpcuser=avinni619 -rpcpassword=avinni619 -datadir=/home/vinni/avineeth/Zcash_work/zcash/vinni/ getinfo
(gdb) bt
No stack.
(gdb)
No stack.
(gdb) b misc.cpp::47
Function “misc.cpp::47” not defined.
Make breakpoint pending on future shared library load? (y or [n]) n
(gdb) b misc.cpp:47
No source file named misc.cpp.
Make breakpoint pending on future shared library load? (y or [n]) n
(gdb) lsit
Undefined command: “lsit”. Try “help”.
(gdb) list
1 : No such file or directory.
(gdb)
1 in
(gdb) info locals
No frame selected.
(gdb)
No frame selected.
(gdb) b rpcwallet.cpp::getbalance
Function “rpcwallet.cpp::getbalance” not defined.
Any insight/inputs would help me to get me startd : )
Regards
Mohit
Did you add the nuparams= to your conf file?
https://zcash.github.io/zcash/dev/regtest.html#network-upgrades
Why would you want to debug zcash-cli, it’s just a simple client which gets console input and makes json-rpc call to a server rpc port (zcashd)? You won’t get far with zcash-cli debugging because it’s zcashd who does all the “heavy lifting”. Anyway, if you want to invoke gdb with an executable which requires arguments, I guess you should use something like gdb --args executablename arg1 arg2 arg3.
In order to build debug version of zcash executables, use CONFIGURE_FLAGS="--enable-debug" zcutil/build.sh -j$(nproc)
P.S. No offense, but it seems you really try hard to avoid reading official documentation 
1 Like
Sure, I will check. Actually I’ve developed a few algorithms which could speed up the underlying computation, say for eg: ECC. Hence, I wanted to know how I could test it? Can you help me to provide any workload?
I’m not the team member, just an user willing to share experience and know-how. Also, I prefer not to involve deeper in zcashd code since end of active development has been announced. Maybe you should join Zcash Research & Development group on Discord and ask further directions how to test and submit your code to the official team for review.
Can you share me the link to join it?
short answer: apt install automake
better answer: RTFM Building Zcashd & Zcash-cli on Debian/Ubuntu — Zcash Documentation 5.7.0 documentation
No @miodragpop we are seeing same error
What linux distro and version you use now? And why do you build zcash binaries again, I thought you’ve passed that already with success? I really don’t understand your workflow logic 
1 Like