- https://splice.com/blog
- https://support.splice.com/hc/en-us
- http://jobs.splice.com
- http://www.billboard.com/articles/news/dance/7392770/splice-sounds-sample-store-feature-innovative-artist-content-dance/
- https://www.npr.org/player/embed/551399290/551399761
- https://www.theverge.com/tech/2017/10/6/16431394/splice-dj-plugins-ozone-8-neutron-2
- http://www.huffingtonpost.com/buster-ross/splice-introduces-beat-ma_1_b_9266648.html
- http://www.bloomberg.com/news/articles/2015-05-21/splice-lets-far-flung-musicians-collaborate-on-songs
- https://splice.com/sounds/splice/andrew-huang-plastic-nature
- https://splice.com/sounds/splice/sounds-of-kshmr-vol-2
- https://www.instagram.com/engineerklee
- https://jobs.splice.com/
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