- https://www.gimmik.net/Magic_Glue,b,153.html
- https://www.gimmik.net/FlySky,b,193.html
- https://www.gimmik.net/Samochody_terenowe_TPC,bc,14,927.html
- https://www.gimmik.net/Zelowe_-_bezobslugowe,k,23,27,120.html
- https://www.gimmik.net/VRX_Racing,b,114.html
- https://www.gimmik.net/Bezszczotkowe_silniki_do_samochodow,k,23,106,503.html
- https://www.facebook.com/wwwgimmikpl
- https://www.instagram.com/gimmik_net
- https://www.youtube.com/user/gimmikpl
- https://www.eraty.pl/do-pobrania/landing-page/proces/
- https://www.gimmik.net/blog/
- http://www.allegro.pl/show_user.php?search=gimmik_pl
- https://www.gimmik.net/
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