- https://tp69.wordpress.com
- https://tp69.blog/category/silent-computer/
- https://tp69.blog/
- https://tp69.blog/author/vrbtn/
- https://tp69.blog/2019/04/23/recovering-from-a-freeze-in-linux/
- https://tp69.blog/2019/02/02/tweaking-python-programs/
- https://tp69.blog/2019/01/16/logging-cron-messages-to-a-different-file/
- https://tp69.blog/2019/01/12/hmm-were-having-trouble-finding-that-site/
- https://tp69.blog/2019/01/01/suppressing-messages-in-var-log-syslog/
- https://tp69.blog/2018/12/31/the-best-way-to-brace-a-wooden-door-or-gate/
- https://tp69.blog/2018/05/15/passively-cooled-cpu-thermals-part-2/
- https://tp69.blog/page/2/
- https://wordpress.com/?ref=footer_custom_svg
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