- https://www.1ka.si/d/sl/o-1ka/pogoji-uporabe-storitve-1ka/politika-piskotkov
- https://www.1ka.si/d/sl/o-1ka/pogoji-uporabe-storitve-1ka
- https://www.1ka.si/admin/survey/index.php?lang=sl
- http://www.1ka.si/
- https://www.1ka.si/d/sl/o-1ka/splosen-opis/nove-funkcionalnosti
- https://www.1ka.si/d/sl/spletne-ankete/knjiga-websm
- https://www.1ka.si/d/sl/spletne-ankete
- https://www.1ka.si/d/sl/novice/2017/iscemo-sodelavce-sodelovanje
- https://www.1ka.si/a/72864
- http://www.facebook.com/pages/1KA/123545614388521?sk=wall
- http://twitter.com/#!/enklikanketa
- https://www.1ka.si/d/sl/o-1ka/splosen-opis
- https://www.1ka.si/d/sl/storitve/cenik-tehnicnih-storitev
- https://twitter.com/enklikanketa
- https://www.facebook.com/1KA-123545614388521/
- https://www.fdv.uni-lj.si/
- https://www.fdv.uni-lj.si/raziskovanje/raziskovalni-centri/oddelek-za-sociologijo/center-za-druzboslovno-informatiko
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