- https://www.scantool.net/
- https://www.scantool.net/customer/account/login/
- https://www.scantool.net/customer/account/create/
- https://www.scantool.net/scan-tools/
- https://www.scantool.net/scan-tools/smart-phone/
- https://www.scantool.net/scan-tools/pc-based/
- https://www.scantool.net/scan-tools/discontinued/
- https://www.scantool.net/software/
- https://www.scantool.net/accessories/
- https://www.scantool.net/accessories/cables/
- https://www.scantool.net/accessories/adapters/
- https://www.scantool.net/development-tools/
- https://www.scantool.net/development-tools/development-boards/
- https://www.scantool.net/development-tools/obd-simulators/
- https://www.scantool.net/development-tools/obd-chips/
- https://www.scantool.net/development-tools/discontinued/
- https://www.scantool.net/forum/
- http://support.scantool.net/support/tickets/new
- https://www.scantool.net/scantool/downloads/
- https://www.scantool.net/faqs/
- https://www.scantool.net/company/
- https://www.scantool.net/contact/
- https://www.scantool.net/blog/
- https://www.scantool.net/obdlink-mxp/
- https://www.scantool.net/obdlink-mxbt/
- https://www.scantool.net/obdlink-lxbt/
- https://www.scantool.net/obdlink-sx/
- https://www.scantool.net/blog/how-do-i-know-whether-my-car-is-obd-ii-compliant/
- https://www.scantool.net/privacy/
- https://www.scantool.net/sales/guest/form/
- https://twitter.com/scantool
- https://business.facebook.com/ScanTool.net/
- https://plus.google.com/+scantoolnet
- https://www.youtube.com/user/scantoolnet
- https://www.linkedin.com/company/obd-solutions?trk=top_nav_home
- https://www.scantool.net/careers/
- https://www.scantool.net/resellers/
- https://www.scantool.net/resellers-apply/
- https://www.scantool.net/payments/
- https://www.scantool.net/shipping-and-returns/
- https://www.scantool.net/warranty/
- https://www.scantool.net/resources/
- http://www.bbb.org/central-northern-western-arizona/business-reviews/auto-diagnostic-service/scantool-net-in-phoenix-az-97005825/#bbbonlineclick
- https://verify.authorize.net/anetseal/?pid=efc328d9-adf7-4cb1-9580-7c1c37d37705&rurl=https%3A//www.scantool.net/scan-tools
- https://www.digicert.com/ev-ssl-certification.htm
- https://www.scantool.net/copyright/
- https://www.scantool.net
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