3 ms·
Nice debugging. Do I understand correctly that the registry reads aren't actually the cause of the problem but rather just a signal that a QNetworkAccessManage
by valleyer 4y ago
Nice debugging. Do I understand correctly that the registry reads aren't actually the cause of the problem but rather just a signal that a QNetworkAccessManager is active and causing a scan?
If so, is there a better routine to break on in the debugger to see it actually initiating a scan?
- muststopmyths 4y agoYou can see a hint in the debugger screenshot. The call is not directly a registry read but to the iphelper API. There are functions in there that enumerate adapters. Knowing nothing about this scanning process, I’m just assuming they first enumerated wireless adapters. So you could start with iphelper and then explore deeper into how you tell the card to scan. There’s probably some API for that as well.
- valleyer 4y agoAh, good point. Wish the backtrace were fully symbolicated (for the system DLLs, at least). Thanks!