- http://lonelyneighbour.pl/
- http://lonelyneighbour.pl/przykladowa-strona/
- http://lonelyneighbour.pl/informacje/
- http://lonelyneighbour.pl/category/kultura-i-plotki/
- http://lonelyneighbour.pl/category/motywacja-i-rozwoj/
- http://lonelyneighbour.pl/category/mysli-emocje/
- http://lonelyneighbour.pl/category/bez-kategorii/
- http://lonelyneighbour.pl/2019/06/16/to-nie-ja/
- http://lonelyneighbour.pl/2019/01/25/862/
- http://lonelyneighbour.pl/2018/12/20/nie-badz-mila/
- http://lonelyneighbour.pl/2018/12/11/851/
- http://lonelyneighbour.pl/2018/11/03/mam-23-lata/
- http://lonelyneighbour.pl/2018/10/22/chce-cie-obchodzic/
- http://lonelyneighbour.pl/2018/10/21/uwielbiam-je/
- http://lonelyneighbour.pl/2018/08/30/wcale-nie-za-wysoko/
- http://lonelyneighbour.pl/2018/08/11/kiedys/
- http://lonelyneighbour.pl/2018/07/29/oddalabym-by-umiec-sie-znow-zachwycic/
- http://lonelyneighbour.pl/page/2/
- http://lonelyneighbour.pl/page/3/
- http://lonelyneighbour.pl/page/10/
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