hm, if I get
load_working_ignetcfg()
right, it does always load a new config when called and free the currently loaded config.
its called from
- the networker client to find out which peers to connect (networker thread)
- the networker client while spooling new messages(networker thread)
- IGNET command NETP checking whether another node calling it is certified (some workerthread)
if both of them do that while the other is stil working with the string, the string is free't and eventually overwritten;
in best case its just stopping before doing all its work,
in worst case it starts reading until eternety.
not that clever.
