Nice project. Will be more useful if there is an explanation of code generated. For example, making the various assembly instructions clickable and displaying information about them. Also a tiny bit of explanation about code and data sections might be of help too :)
You don't filter out CPP macro's. I would skip that and only allow C code. Or run this thing in a proper jail because at the moment:
- doing an include #include "/dev/random" will block the thread.
- including "/etc/passwd" is also possible although I don't see a direct way to turn this into password disclosure.
Seriously; even if it's a weekend project, letting people run all kinds of potentially bad code on your machine is never a good idea. Even though you don't run the binaries yourself there's so many ways to mess around with a compiler. You just don't know what's going to happen.
Saying "you can read /etc/shadow by doing X, Y, and Z" is okay -- it's a permanent record there was a flaw. Saying "here's your root password hash" is not ok; even once the flaw is fixed, that hash is still floating around out there. I'd take advantage of the edit period and remove that from your comment; it's just not cool. The OP should definitely change the root password on the box regardless.
This could be a great educational tool! It could be used to teach Introductory Computer Organization at the college level.
I have a suggestion:
- Would you be able to separate the web interface, so that it could used to display Java -> JVM assembly, or any other language. Basically, so that it would be re-usable.
Definitely interesting! Lots of us unix people would just run objdump -d for a quick ASM extraction, but this is probably much friendlier to the user just starting to learn C/ASM.
Can i recommend adding -masm=intel to your gcc flags? I know AT&T syntax is the default for gcc and gas, but not why. Intel syntax seems clearer to read and is used by most assembly tutorials.
This really removes any hurdle I might have of inspecting the assembly code due to sheer laziness of opening up my Visual Studio and start debugging. Awesome work. If you add some type of interactivity to the generated assembly, it can be made more visual.
My only suggestion right now is to have it so you can have the assembly on the left or right side. Maybe it's just me, but my focus seems to be on the left side more than the right.
Since this is a focused on assembly it seems, wouldn't you want the focus on the assembly, not the C? It could be different for different people though.
Very neat! Suggestion: add a 'flags' field where you can specify stuff like -std=c99 and any other flags you might need for your code to compile, and a horizontal rule or something like that after every line of input code.
If you do the 'flags' thing make sure you filter it to avoid escapes to the underlying shell.
Error: Command failed: /tmp/test969394043.c:1:0: fatal error: can’t open /root/assembler/ccMEBJ3B.s for writing: Permission denied
compilation terminated.
The bug is not reproducible, so it is likely a hardware or OS problem.
Interesting project. As an improvement to the UI, you can consider adding syntax highlighting to the editor. Take a look at ACE editor (http://ace.ajax.org/).
don't work really - some guidance on use might be acceptable. does it need to be a whole program? my snippets give confusing errors about variable identifiers not being types o_0
excellent -- my unsolicited advice is for you to ping some professors and TAs who teach low-level programming to get them interested in using this in their teaching.
you can compile C/C++ to LLVM IR and also 32 or 64 bit intel assembler. you can also see the effects of different optimizations, etc