Show HN: Online C/C++ to assembly visualizer [Weekend Project]
1–10 of 47 posts
Re: Show HN: Online C/C++ to assembly visualizer [Weekend Project]
#2Re: Show HN: Online C/C++ to assembly visualizer [Weekend Project]
#3Nice 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 :)
Re: Show HN: Online C/C++ to assembly visualizer [Weekend Project]
#4Re: Show HN: Online C/C++ to assembly visualizer [Weekend Project]
#5Re: Show HN: Online C/C++ to assembly visualizer [Weekend Project]
#6Nice 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 :)
Ok added to the todo list
- 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.
Re: Show HN: Online C/C++ to assembly visualizer [Weekend Project]
#7Re: Show HN: Online C/C++ to assembly visualizer [Weekend Project]
#8Nice 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 :)
Re: Show HN: Online C/C++ to assembly visualizer [Weekend Project]
#9Try this on iPad. Generated assembly looks very bad in terms of layout.
Re: Show HN: Online C/C++ to assembly visualizer [Weekend Project]
#10Earlier quoted context omitted.
Ok added to the todo list
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 ma…
Having the actual CPP available is nice because some bits of libc are only macros.