- https://google.az
- https://store.google.com/?utm_source=hp_header&utm_medium=google_oo&utm_campaign=GS100042
- https://mail.google.com/mail/?tab=wm
- https://www.google.com/imghp?hl=en&tab=wi
- https://www.google.com/intl/en/about/products?tab=wh
- https://accounts.google.com/ServiceLogin?hl=en&passive=true&continue=https://www.google.az/
- https://www.google.az/setprefs?sig=0_AaApzspfkeXwgGfyj8y-tAE08KY%3D&hl=az&source=homepage&sa=X&ved=0ahUKEwjd6tvhvbriAhWKnOAKHdOEAfkQ2ZgBCAk
- https://www.google.az/intl/en_us/policies/privacy/?fg=1
- https://www.google.az/intl/en_us/policies/terms/?fg=1
- https://www.google.az/preferences?hl=en
- https://www.google.az/preferences?hl=en&fg=1
- https://www.google.az/intl/en_us/ads/?subid=ww-ww-et-g-awa-a-g_hpafoot1_1!o2&utm_source=google.com&utm_medium=referral&utm_campaign=google_hpafooter&fg=1
- https://www.google.az/services/?subid=ww-ww-et-g-awa-a-g_hpbfoot1_1!o2&utm_source=google.com&utm_medium=referral&utm_campaign=google_hpbfooter&fg=1
- https://myaccount.google.com/?utm_source=OGB&tab=wk&utm_medium=app
- https://www.google.com/webhp?tab=ww
- https://maps.google.com/maps?hl=en&tab=wl
- https://www.youtube.com/?gl=US
- https://play.google.com/?hl=en&tab=w8
- https://news.google.com/nwshp?hl=en&tab=wn
- https://contacts.google.com/?hl=en&tab=wC
- https://drive.google.com/?tab=wo
- https://www.google.com/calendar?tab=wc
- https://translate.google.com/?hl=en&tab=wT
- https://photos.google.com/?tab=wq&pageId=none
- https://www.google.com/shopping?hl=en&source=og&tab=wf
- https://www.google.com/finance?tab=we
- https://docs.google.com/document/?usp=docs_alc
- https://books.google.com/bkshp?hl=en&tab=wp
- https://www.blogger.com/?tab=wj
- https://duo.google.com/?usp=duo_ald
- https://hangouts.google.com/
- https://keep.google.com/
- https://jamboard.google.com/?usp=jam_ald
- https://earth.google.com/web/
- https://www.google.com/save
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