- https://twitter.com/HajMinistry
- https://www.youtube.com/channel/UCCm8-SFjGg7Fb13CQT1GFOg
- http://maqam.sa
- https://localhaj.haj.gov.sa/LHB/pages/home.xhtml?dswid=-4166
- https://ehaj.haj.gov.sa/EH/index.xhtml?dswid=-4249
- https://volunteer.haj.gov.sa
- https://mawsim.haj.gov.sa
- https://play.google.com/store/apps/details?id=com.hajj.manasikana
- http://vro.haj.gov.sa/Arabic/Pages/default.aspx
- https://www.my.gov.sa/wps/portal/snp/main
- http://www.mofa.gov.sa/
- https://www.moi.gov.sa/
- http://www.makkah.gov.sa/
- https://www.gph.gov.sa/
- http://www.moh.gov.sa/Pages/Default.aspx
- https://gaca.gov.sa/web/ar-sa/page/home
- http://www.imaratalmadinah.gov.sa/
- http://mci.gov.sa/Pages/default.aspx
- http://www.adahi.org/Arabic/Pages/default.aspx
- http://vro.haj.gov.sa/arabic/Pages/default.aspx
- https://ehaj.haj.gov.sa/EH/index.xhtml;jsessionid=xex827Zsixldwz0tVQ0KI099?dswid=6097
- http://localhaj.haj.gov.sa/LHB/pages/home.xhtml?dswid=9858
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