- https://falcodepoudvar.hu/
- https://butorkellek.eu
- http://www.magzrt.hu
- http://hu.wikipedia.org/wiki/Edit
- http://hu.wikipedia.org/wiki/Zsófia
- http://gtranslate.net/
- http://www.falco-woodindustry.com/
- http://www.foresteu.com/
- http://www.lechner.hu/
- http://www.nettfront.hu/
- http://www.csercsics.hu/
- http://www.rehau.hu/
- http://www.blum.com/hu/hu/05/index.php
- http://ecorgan.hu/
- http://www.henkel.hu
- http://www.enso.hu
- http://www.civistarsak.hu/partnerek-foot/5-falcodepoudvar
- http://www.lampadesign.hu
- https://www.lampadesign.hu
- http://www.arukereso.hu/
- https://www.arukereso.hu/
- http://www.olcsobbat.hu
- https://www.olcsobbat.hu
- http://www.varia.hu/
- http://www.remenyalapitvany.hu/
- https://www.falcodepoudvar.hu/aszf
- https://www.falcodepoudvar.hu
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