Sometimes it returns a static string like `g_str_int` and sometimes a newly heap-allocated string, such as returned by `class_type_array_name(g_str_int, depth)`.
Callers have no way to properly release the memory allocated by this function.
neocanable 36 days ago [-]
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.
norir 36 days ago [-]
Many command line tools do not need memory management at all, at least to first approximation. Free nothing and let the os cleanup on process exit. Most libraries can either use an arena internally and copy any values that get returned to the user to the heap at boundaries or require the user to externally create and destroy the arena. This can be made ergonomic with one macro that injects an arena argument into function defs and another that replaces malloc by bumping the local arena data pointer that the prior macro injected.
1718627440 36 days ago [-]
That might be true, but leaking is neither the critical nor the most hard to find memory management issue, and good luck trying to adapt or even run valgrind with a codebase that mindlessly allocates and leaks everywhere.
kevin_thibedeau 36 days ago [-]
Shhh. We want the ML models trained on this sort of deeply flawed code.
guerrilla 36 days ago [-]
Pretty sure you can just disable leak checking.
1718627440 36 days ago [-]
But for example verifying that memory is not touched after it is supposed to, is much harder when you can't rely on it being freed.
Of course literally running valgrind is still possible, but it is difficult to get useful information.
nick__m 36 days ago [-]
You cannot have use-after-free if you never call free, so there are no points at which memory should not be touched.
That's the beauty of the never free memory management strategy.
dajtxx 36 days ago [-]
It can still be a bug if you use something after you would have freed it because your code isn't meant to be using that object any more. It points to errors in the logic.
guerrilla 35 days ago [-]
Agreed. I think being methodical is better here for sure.
IshKebab 36 days ago [-]
Interesting. Someone should come up with a language that prevents these sorts of mistakes!
cenamus 36 days ago [-]
Thank god Lisp is older than C, don't have to deal with such nonsense :-)
brabel 36 days ago [-]
That’s impossible. Just be more careful and everything should work, the author’s C was just a bit rusty!
neocanable 36 days ago [-]
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.
sim7c00 36 days ago [-]
u did really well ppl like to pick on C. :) thanks for making it in C, fun to read ur code and see how others go about this language!
kookamamie 36 days ago [-]
Yes, perhaps it could have a marketing slogan like "Write once, crash everywhere!"
uecker 36 days ago [-]
I think he is using memory pools, so this is ok.
pjmlp 36 days ago [-]
If only there were a couple of OSes implementated during the 1960's with such programming languages....
kazinator 35 days ago [-]
In the same file:
static bool is_java_identifier_start(char c)
{
return (isalpha(c) || c == '_' || c == '$');
}
Undefined behavior in isalpha if c happens to be negative (and not equal to EOF), like some UTF-8 byte.
I think some <ctype.h> implementations are hardened against this issue, but not all.
masfoobar 35 days ago [-]
> I am always curious how different C programs decide how to manage memory.
At a basic level, you can create memory on the stack or on the heap. Obviously I will focus on the heap as that is dynamically allocating memory of a certain size.
The C programming language does not force you how to handle memory. You are pretty much on your own. For some C programmers (and likely more inexperienced ones) they will malloc individual variables like they are creating a 'new' instance in a typical OOP language like Java. This can be a telltale sign of a programmer working with C that comes from an OOP background. As they learn and improve on their C skills they realise they should create a chunk of memory of a certain type, but could still be malloc(ing) and free(ing) all over the code, making it difficult to understand what is being used and where -- especially if you are looking at code you did not write.
You can also have programs that do not bother free(ing) memory. For example, a simple shell program that just does simple input->process->output and terminates. For these types of programs, just let the OS deal with freeing the memory.
Good C code (in my opinion) uses malloc and free in only a handful of functions. There are higher level functions for proper Allocators. One example is an Arena Allocator. Then if you want a function which may require dynamic memory, you can tell it which allocator to use. It gives you control, generally speaking. You can create a simple string library or builder with an allocator.
Of course an Allocator does not have to use memory on the heap. It can still use on the stack as well.
There are various other patterns to use in the world of memory, especially in C.
SunlitCat 36 days ago [-]
Strings! The bane of C programming, and a big reason I prefer C++. :D
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.
Koshkin 36 days ago [-]
> 10 times faster than that of Java
I was hoping that these days' Java would be "almost" as fast C/C++. Oh well.
neocanable 35 days ago [-]
In the process of writing this, I learned a lot about JVM. JVM has done well enough, even surpassing C/C++ in some cases.
mdaniel 36 days ago [-]
This has been my life experience with things written in C/C++, so speed doesn't matter. Or, I guess from an alternative perspective, it ran very fast, but exited very fast, too :-D
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.
uecker 36 days ago [-]
Is it? This is my experience with Python. The C/C++ programs I use daily never seem to crash (Linux, bash, terminals, X, firefox, vim, etc.). It must be years ago one of those programs crashed while I used it.
1718627440 36 days ago [-]
Also a segfault IS the protection layer intervening, it is equivalent to a exception in other languages. The real problem is, when there is no segfault.
uecker 36 days ago [-]
This is absolutely true. But even this does not happen in the software I use every day. Software written is C is definitely the most stable I use - by far. That there are people running around claiming that it is impossible to write stable software in C and it crashes all the time due to bugs is rather unfortunate, as it is far from the truth.
tslater2006 36 days ago [-]
The readme shows support for dumping dex files. Edit: missed that it has a comment that stays "unsupport for now" but at least it looks like something planned
neocanable 36 days ago [-]
It is processes inner classes recursively. First read all entry from jar, and analyze the relationships between classes. Then do some decompile job.
neocanable 26 days ago [-]
the project support dex and apk now.
36 days ago [-]
stefanos82 36 days ago [-]
Nice job! I don't know whether you know https://github.com/java-decompiler/jd-gui or not, but in case you haven't seen it before, maybe you could use it as a reference, since it's written in Java, for extra fun with your adventure?
rafram 36 days ago [-]
Things may have changed, but my impression as of several years ago was that JD-GUI was far, far behind the state of the art (Fernflower, aka the built-in IntelliJ decompiler) in terms of correctness, re-sugaring, support for modern Java features, and so on. Fernflower is open source as part of IntelliJ: https://github.com/fesh0r/fernflower
GranPC 36 days ago [-]
Is there a good GUI for this a la jadx-gui that isn't an entire IDE?
rafram 36 days ago [-]
Not that I know of. The features I'd want in order to consider a decompiler GUI "good" (e.g. a good text editing control, go-to-definition, find usages, manual renaming of obfuscated symbol names) quickly approach the scope of an entire IDE, though.
DefineOutside 36 days ago [-]
The most feature advanced decompiler I know of is Recaf. It supports a mix of decompilers and even bytecode editing.
GranPC 35 days ago [-]
This looks excellent. I'll be sure to try it out. Thanks!
By hand or with AI? Fascinating. So much work! What was your motivation for this?
neocanable 36 days ago [-]
90% by hand, 10% AI. I do this for fun and to learn about jvm.
jebarker 36 days ago [-]
I think that sort of ratio is the sweet spot for learning. I've been writing an 8086 simulator in C++ and using an LLM for answering specific technical questions I come up with has drastically sped up my progress without it actually doing the work for me.
keepamovin 36 days ago [-]
Wow, impressive. A project of the scale and depth.
xandrius 36 days ago [-]
Irrelevant to me. People would never ask whether someone has created something looking at SO or not. If the thing works as advertised, good for them!
lyxell 36 days ago [-]
To some people the process leading to a finished project is the most interesting thing about posts like these.
johnisgood 36 days ago [-]
LLMs can explain the process, and you can build projects with LLMs explaining the process.
nticompass 36 days ago [-]
LLMs can attempt to explain the code, but it can't explain people's thought process and that's the interesting part.
I want to hear about the reverse engineering, how you thought the code through. LLMs are boring.
johnisgood 36 days ago [-]
They can, if you write down your thought process, which is probably what you should do when you are using an LLM to create a product, but what do I know.
Ghoelian 36 days ago [-]
> They can, if you write down your thought process
Just write a blogpost at that point.
johnisgood 36 days ago [-]
You do not have to be as accurate or that specific, you do not have to worry about the way you word or organize things, the LLM can figure it out, as opposed to a blog post.
So "To some people the process leading to a finished project is the most interesting thing about posts like these." is bullshit, that is said by someone who has never used LLM properly. You can achieve it with LLMs. You definitely can, I know, I did, accurately (I double checked).
How come? You had different experiences? Which LLMs, what prompts? Give me all the details that supports your claim that it is not true. My experiences completely differ from yours, so the way I use it, it is very much true.
That said, it is probably pointless to argue with full-blown AI-skeptics.
People had lots of great and productive-enhancing experiences with LLMs, you did not, great, that does not reflect the tool, it reflects your way of using the tool.
It's not about explaining the process but experiencing it.
johnisgood 36 days ago [-]
Well, they can experience it if they wish to. Sadly most vibe-coders do not.
shortrounddev2 36 days ago [-]
LLM output is simply not interesting
johnisgood 36 days ago [-]
I did not say that you should copy paste its output verbatim. I thought this was obvious.
Additionally, "interesting" is highly subjective. It could be technically correct, yet uninteresting.
Bjartr 36 days ago [-]
A great question to ask. We're in the middle of learning where AI can and can't be effective. Knowing where and how it's being used is quite useful.
ConanRus 36 days ago [-]
Can you also write a C decompiler in pure Java language?
dardeaup 36 days ago [-]
Of course it can be done! It wouldn't be as general purpose as the Java decompiler in C because the C decompiler would have to know about the CPU architecture of the executable code (just as the Java decompiler has to know about JVM opcodes).
Do you have a scanner that checks these sorts of things or is it something that you are passionate about?
kazinator 35 days ago [-]
By the following very short garden path:
1. How silly to write such a thing in C from scratch. Such a project will invariably invent half of Lisp in order to have the right kind of infrastructure for doing this and that.
2. Let's look for some of it up and down the tree. Oh look, there is a bitset and hashmap, see? I don't see test cases for these anywhere; is it original work from this project or battle-tested code taken from elsewhere?
3. Open hashmap.c ...
GPL violation found in half a minute.
issafram 35 days ago [-]
Yea I'm not criticizing you. Was just genuinely curious. Thanks
Yea I saw that after looking it up. I wasn't questioning the statement, but me personally I wouldn't look at each file and look for license violations. That's all.
26 days ago [-]
yusina 36 days ago [-]
[flagged]
36 days ago [-]
bongodongobob 36 days ago [-]
[flagged]
kamma4434 36 days ago [-]
I cannot help but wonder why starting a new project in C in 2025. It’s like driving a car with no seat belts. You sure you want to do that?
uecker 36 days ago [-]
I moved from C++ to C and I am more productive. I also think this "no seat belts" meme is exaggerated, as there are plenty of tools and strategies to make C fairly safe to use. (it is true though that many people do not put the seat belts on).
zzo38computer 36 days ago [-]
In my experience, although many of the other programming languages do improve some things compared with C, they also make many things worse and avoid some of the benefits of C programming.
pjmlp 36 days ago [-]
I can't recall anything in that sense regarding Modula-2 and Object Pascal, other than not bringing UNIX to the party.
UncleEntity 36 days ago [-]
I cannot help but wonder why I would learn a whole new language before even beginning to start a new project when I already know C. Though, generally speaking, I tend to use C++ for new projects -- usually depending on what libraries I'm using, if the lib is in C I use C and if the lib is in C++ I use C++. The current thing I'm working on is intended as a Python extension module and Python is written in C so...
And, yes, I know it's trivial to interface the Python C-API with C++ and quite often better as the 'object model' is very similar but the underlying concept I wanted to explore (guaranteed tailcalls) isn't possible in C++ from what I can tell.
ronsor 36 days ago [-]
Yes, yes I'm sure. I like using C sometimes.
neocanable 35 days ago [-]
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.
userbinator 35 days ago [-]
Or riding a motorcycle.
But stupid real-world analogies are stupid.
sim7c00 36 days ago [-]
i only write in C. if id build a car it wouldnt have seatbelts. boring, put in ejector seats! not safe? no problem for C :).
SunlitCat 36 days ago [-]
ejector seats in C car?
goto eject;
...more code we are going to ignore, it could be important but nah, ignore it, what could be happen?...
eject:
up_through_the_roof();
:D
Sophira 36 days ago [-]
We need people who can (and do) write in C, assembly, and all these low-level languages. Otherwise, software will just get slower and slower.
AgentME 36 days ago [-]
Rust has the same low-level memory model as C without the footguns.
dardeaup 36 days ago [-]
Rust certainly does have some improvements, but I'm not 100% certain that it's the best tool for all low-level software. For example, I'm experimenting with Rust for some filesystem type code and I can't figure out how to write/read a struct to/from disk all at once. I'm brand new to Rust, so it's quite possible that it can be done and I just don't know the technique. Basically, I'm looking for something in Rust analogous to C's fread/fwrite. I know I can write out each field of the struct individually, but when the struct has many fields it means having to write a huge amount of nasty boilerplate code when in C it's a single function call (fread/fwrite).
whytevuhuni 35 days ago [-]
This is generally unsafe, so to make it safe there needs to be something that restricts what kind of things you can read and write.
For example, if your structure contains a reference, and you read an instance of that from disk, then you now have a potentially invalid reference, bypassing Rust's guarantees. Reading a structure of i32 numbers is safe, but it also has endianness footguns.
The zerocopy crate implements traits and gives you a derive macro to mark types as being safe to serialize/deserialize in a safe way.
saintfire 36 days ago [-]
I think you're going to want to reach for serde.
Its a bit of annotating but you can then de/serialize structs to arbitrary formats with one call.
dardeaup 36 days ago [-]
Thanks for the suggestion! I'll have a look.
ramon156 35 days ago [-]
I love Rust but we really got to stop the link between C and Rust.
If someone mentions C, that's not a free invite to start educating them on why they SHOULD use Rust. No one at the party is going to talk to you again that night
hualaka 35 days ago [-]
When debugging complex projects, the C language is more flexible and convenient to view data in memory.
lsferreira42 35 days ago [-]
It's thanks to people like you that rust is not more widely used, you actively make people avoid the rust cummunity because they will think everybody i like you!
In this case there are is a custom string library. Functions returned owned heap-allocated strings.
However, I think there's a problem where static strings are used interchangably with heap-allocated strings, such as in the function `string class_simple_name(string full)` ( https://github.com/neocanable/garlic/blob/72357ddbcffdb75641... )
Sometimes it returns a static string like `g_str_int` and sometimes a newly heap-allocated string, such as returned by `class_type_array_name(g_str_int, depth)`.
Callers have no way to properly release the memory allocated by this function.
Of course literally running valgrind is still possible, but it is difficult to get useful information.
That's the beauty of the never free memory management strategy.
I think some <ctype.h> implementations are hardened against this issue, but not all.
At a basic level, you can create memory on the stack or on the heap. Obviously I will focus on the heap as that is dynamically allocating memory of a certain size.
The C programming language does not force you how to handle memory. You are pretty much on your own. For some C programmers (and likely more inexperienced ones) they will malloc individual variables like they are creating a 'new' instance in a typical OOP language like Java. This can be a telltale sign of a programmer working with C that comes from an OOP background. As they learn and improve on their C skills they realise they should create a chunk of memory of a certain type, but could still be malloc(ing) and free(ing) all over the code, making it difficult to understand what is being used and where -- especially if you are looking at code you did not write.
You can also have programs that do not bother free(ing) memory. For example, a simple shell program that just does simple input->process->output and terminates. For these types of programs, just let the OS deal with freeing the memory.
Good C code (in my opinion) uses malloc and free in only a handful of functions. There are higher level functions for proper Allocators. One example is an Arena Allocator. Then if you want a function which may require dynamic memory, you can tell it which allocator to use. It gives you control, generally speaking. You can create a simple string library or builder with an allocator.
Of course an Allocator does not have to use memory on the heap. It can still use on the stack as well.
There are various other patterns to use in the world of memory, especially in C.
I guess there's some history there that I'm not familiar with because JBoss also has a FernFlower decompiler library https://mvnrepository.com/artifact/org.jboss.windup.decompil...
> Examples of Vineflower's output, compared to other decompilers, can be found on the wiki.
[wiki is empty]
:-/
Any plan to support `.dex` in the future? Also curious how you handle inner classes inside JARs.
It seems someone liked it and made a "v2" along with LSP support https://github.com/A-LPG/LPG2#lpg2
https://www.jikesrvm.org/
I was hoping that these days' Java would be "almost" as fast C/C++. Oh well.
I want to hear about the reverse engineering, how you thought the code through. LLMs are boring.
Just write a blogpost at that point.
So "To some people the process leading to a finished project is the most interesting thing about posts like these." is bullshit, that is said by someone who has never used LLM properly. You can achieve it with LLMs. You definitely can, I know, I did, accurately (I double checked).
I will throw it out here, too: https://news.ycombinator.com/item?id=44163063 (My AI skeptic friends are all nuts)
That said, it is probably pointless to argue with full-blown AI-skeptics.
People had lots of great and productive-enhancing experiences with LLMs, you did not, great, that does not reflect the tool, it reflects your way of using the tool.
I will just throw it out here: https://news.ycombinator.com/item?id=44163063 (My AI skeptic friends are all nuts)
Additionally, "interesting" is highly subjective. It could be technically correct, yet uninteresting.
https://opensource.stackexchange.com/questions/10737/inclusi...
Do you have a scanner that checks these sorts of things or is it something that you are passionate about?
1. How silly to write such a thing in C from scratch. Such a project will invariably invent half of Lisp in order to have the right kind of infrastructure for doing this and that.
2. Let's look for some of it up and down the tree. Oh look, there is a bitset and hashmap, see? I don't see test cases for these anywhere; is it original work from this project or battle-tested code taken from elsewhere?
3. Open hashmap.c ...
GPL violation found in half a minute.
And, yes, I know it's trivial to interface the Python C-API with C++ and quite often better as the 'object model' is very similar but the underlying concept I wanted to explore (guaranteed tailcalls) isn't possible in C++ from what I can tell.
But stupid real-world analogies are stupid.
goto eject; ...more code we are going to ignore, it could be important but nah, ignore it, what could be happen?...
eject: up_through_the_roof();
:D
For example, if your structure contains a reference, and you read an instance of that from disk, then you now have a potentially invalid reference, bypassing Rust's guarantees. Reading a structure of i32 numbers is safe, but it also has endianness footguns.
The zerocopy crate implements traits and gives you a derive macro to mark types as being safe to serialize/deserialize in a safe way.
If someone mentions C, that's not a free invite to start educating them on why they SHOULD use Rust. No one at the party is going to talk to you again that night