neocanable

Thank you for your attention!

Thanks for your advice.

Thanks for your advice!!!

It is really hard for programmers

got it, thank you, I hidden it.

The decompiler support android apk and dex now

the project support dex and apk now.

yes, support android apk and dex now

This is the best question for me. Writing these codes in C language is the best way to learn the file structure of jvm/dalvik/pe. This process makes me like C language more. For me, I think it is simple and pure, which is enough.

In the process of writing this, I learned a lot about JVM. JVM has done well enough, even surpassing C/C++ in some cases.

This project is my first project written in C language. Before this, my C language level was only at printf("hello world"). I am very happy because this project made me dare to use secondary pointers.

In multi-threaded mode, each thread will create a separate memory pool. If in single-threaded mode, a global memory pool is used. You can refer to https://github.com/neocanable/garlic/blob/72357ddbcffdb75641.... The x_alloc and x_alloc_in in it indicate where the memory is allocated. When each task ends, the memory allocated in the memory pool is released, and the cycle repeats.

Sorry for giving you a bad experience. Please provide the jar file or class file. I hope I can fix it as soon as possible.

90% by hand, 10% AI. I do this for fun and to learn about jvm.

It is processes inner classes recursively. First read all entry from jar, and analyze the relationships between classes. Then do some decompile job.

I am writing the part of decompiling dex and apk. The current speed is about 10 times faster than that of Java, and it takes up less resources than Java. And the compiled binary is smaller, only about 300k. Thank you for your attention.