- http://protos.ru/
- http://protos-textile.ru
- http://protos.ru/delivery.php
- http://protos.ru/price.php?n=293&d=all
- http://protos.ru/price.php
- http://protos.ru/price.php?n=477&d=all
- http://protos.ru/coordinat.php
- http://maps.yandex.ru/-/CVRHr8m0
- http://vk.com/club23478207
- https://twitter.com/polonskaya2
- http://www.facebook.com/pages/%D0%A8%D0%B2%D0%B5%D0%B9%D0%BD%D0%B0%D1%8F-%D1%84%D1%83%D1%80%D0%BD%D0%B8%D1%82%D1%83%D1%80%D0%B0-PROTOS-Co/178287335538860?ref=hl
- https://www.instagram.com/protos_furnitura
- http://rusport.ru/
- http://u3687.23.spylog.com/cnt?cid=368723&f=3&p=1
- http://top.mail.ru/jump?from=330618
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