- http://sibran.ru
- http://market.sibran.ru/personal/cart/
- http://sibran.ru/login/?backurl=%2F
- http://sibran.ru/login/?register=yes&backurl=%2F
- http://sibran.ru/about/
- http://sibran.ru/
- http://sibran.ru/congratulations/
- http://sibran.ru/news/
- http://sibran.ru/catalog/
- http://sibran.ru/journals/
- http://market.sibran.ru/catalog/
- http://sibran.ru/progress/
- http://sibran.ru/editors/editor_for.php
- http://sibran.ru/purchase.php
- http://sibran.ru/personal/provision/
- http://sibran.ru/about/links/
- http://sibran.ru/en/
- http://www-sbras.nsc.ru
- http://www.sbras.info
- https://metrika.yandex.ru/stat/?id=27151751&from=informer
- https://money.yandex.ru
- http://promsoft.ru/
After the rust string overview of its internal substructures, let's see if c++ QString storage is more light, but first we'r going to take a look to the c++ standard string object: At first sight we can see the allocation and deallocation created by the clang++ compiler, and the DAT_00400d34 is the string. If we use same algorithm than the rust code but in c++: We have a different decompilation layout. Note that the Ghidra scans very fast the c++ binaries, and with rust binaries gets crazy for a while. Locating main is also very simple in a c++ compiled binary, indeed is more low-level than rust. The byte array is initialized with a simply move instruction: 00400c4b 48 b8 68 MOV RAX,0x6f77206f6c6c6568 And basic_string generates the string, in the case of rust this was carazy endless set of calls, detected by ghidra as a runtime, but nevertheless the basic_str...
Comments