- http://mymusic.com.ng/subscribe.php?source=home
- http://www.mymusic.com.ng/blog/?p=11486
- http://thenextweb.com/insider/2013/11/05/startups-outside-western-europe-attend-western-european-tech-conferences-asked-around-dublin-web-summit/
- https://www.bloomberg.com/news/articles/2015-10-20/nigeria-s-answer-to-spotify-lures-investors-from-mtn-to-jay-z
- https://www.youtube.com/watch?v=mpit32bnYwY
- http://edition.cnn.com/2013/11/28/tech/nigerian-itunes-dances-mobile-beat/
- http://venturesafrica.com/innovators#damola-taiwo-tola-ogunsola-dolapo-taiwo
- https://www.facebook.com/mymusicng
- https://www.instagram.com/mymusicafrica
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