- https://go.proz.com/professional-membership
- https://www.facebook.com/prozdotcom
- https://www.linkedin.com/company/proz-com
- https://www.twitter.com/prozcom
- https://go.proz.com/blog
- https://www.tm-town.com/
- https://chi.proz.com/?set_site_lang=chi
- https://deu.proz.com/?set_site_lang=deu
- https://esl.proz.com/?set_site_lang=esl
- https://fra.proz.com/?set_site_lang=fra
- https://ita.proz.com/?set_site_lang=ita
- https://hun.proz.com/?set_site_lang=hun
- https://dut.proz.com/?set_site_lang=dut
- https://pol.proz.com/?set_site_lang=pol
- https://por.proz.com/?set_site_lang=por
- https://ron.proz.com/?set_site_lang=ron
- https://ces.proz.com/?set_site_lang=ces
- https://rus.proz.com/?set_site_lang=rus
- https://ara.proz.com/?set_site_lang=ara
- https://jpn.proz.com/?set_site_lang=jpn
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