- https://www.pcac.org.uk
- https://www.pcac.org.uk/
- https://www.pcac.org.uk/who-we-help-1/
- https://www.pcac.org.uk/degree-level/
- https://www.pcac.org.uk/school/
- https://www.pcac.org.uk/children/
- https://www.pcac.org.uk/students/
- https://www.pcac.org.uk/how-to-get-help/
- https://www.pcac.org.uk/process-info/
- https://www.pcac.org.uk/enquiry/
- https://www.pcac.org.uk/about-us/
- https://www.pcac.org.uk/staff/
- https://www.pcac.org.uk/support-us/
- https://www.pcac.org.uk/general-donations/
- https://www.pcac.org.uk/gift-aid-2/
- https://www.pcac.org.uk/leaving-a-legacy-2/
- http://www.professionalsaid.org.uk/who-we-help-1/
- http://pcac.org.uk/process-info/
- http://pcac.org.uk/how to get help/
- http://pcac.org.uk/who-we-help-1/
- http://pcac.org.uk/how-to-get-help/
- http://pcac.org.uk/about-us/
- http://pcac.org.uk/support-us/
- http://pcac.org.uk/accessibility-policy/
- http://pcac.org.uk/privacy-notice
- http://pcac.org.uk/site-map/
- https://www.pcac.org.uk/privacy-notice/
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