- http://www.dexcraft.pl/
- http://dexcraft.pl/
- http://dexcraft.pl/content/4-o-nas
- http://dexcraft.pl/kompozyty-weglowe/83-elementy-z-carbonu-laminat-weglowy-wlokno-weglowe-wyroby.html
- http://dexcraft.pl/content/22-technologie-prepreg-infuzja-zywicy-reczne-laminowanie-produkcja
- http://dexcraft.pl/content/29-zaplecze-i-mozliwosci-kompozyty-weglowe
- http://dexcraft.pl/content/11-porady
- http://dexcraft.pl/kontakt
- http://dexcraft.pl/sklep
- http://www.dexcraft.com
- http://www.facebook.com/Dexcraft
- https://instagram.com/dexcraft_carbon_fiber/
- https://www.google.com/maps?ll=52.379057,21.232&z=15&t=m&hl=pl&gl=PL&mapclient=embed&q=Helen%C3%B3w+13+05-200+Helen%C3%B3w
- http://www.dexcraft.pl/content/4-o-nas
- http://www.dexcraft.com/root-category/83-elementy-z-wlokna-weglowego-wlokno-weglowe-produkcja.html
- http://www.dexcraft.pl/content/13-hamownia-doloty-projektowane-na-hamowni-wykres-mocy
- http://www.dexcraft.com/shop
- https://www.4pixel.pl/
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