justanotheranonymoususer
justanotheranonymoususer
I second this request.
> The correct expression is `mydll:.100`. OK, thanks. The problem is that the auto suggest shows otherwise, so it's not intuitive and difficult to know.
Yes, graph view rarely fails :) but the mis-marking also bothers in that if I click "g" in the non-marked spot, it shows from the middle of the func, P.S....
Here's this file: [will expire in 30 days](https://easyupload.io/8a4xhe), [hash and info](https://www.virustotal.com/gui/file/46351bd350799dc196481cbe2b26f628b489a280a9e2f49bace71930f3dc80d3/detection) Function from MS PDB: `private: bool __cdecl LOCATOR::FLocateCvFilePathHelper(unsigned short const * __ptr64,unsigned short const * __ptr64,unsigned __int64,bool) __ptr64` RVA:...
Hmm, I downloaded the latest build, even though mine is quite recent, and you're right, it looks fine. Except I don't see the loops, is that a plugin, or some...
Well, yeah, I'm using Ctrl+A since forever, it's sad news that it's not supported anymore :( any plans on reviving it? It's much more convenient to have all functions analyzed...
Wait, does that mean that x-ref detection in whole module is not supported too? That's kinda essential and sad.
> What is your use case for having all functions analyzed? It's just convenient to be able to press Ctrl+A and be done with the analysis. Then I can debug...