how to get the byte code or machine code
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
Menu
▾
▴
in visual c++ i can get the byte code or machine code while doing the debug with step over option, but just wonder in dev c++ can view the byte code or not???
Please advice!!
Hi Clifford Brother,
I dun know why i'm learning shellcode make u so angry,learning exploit still programming right,like socket programming.I just want to know whether dev c++ able to retrieve the program's byte code,is it wrong??
Anyway i really appreciate ur help and i had learn some thing here ,e.g insight debugger.
So i think this post need to close,thanks all!!
LTC
Learning exploit actually is not consider "programming malicious code",it is like a "sword", it can kill people but also can protect people.
Most of the security researcher learn how to audit program,analyze,find bug,then create proof of concept(exploit).
Brother Clifford,i think u r too sensitive in this topic.I didn't say that i'm going to use this knowledge to do criminal activity.
Take easy man,take easy!
I am neither a monk nor a relation to you, so you can stop referring to me as "brother".
So you are are "security researcher" then? I doubt that somehow.
The information you seek is no doubt easily available, but that does not mean that it should be propagated or discussed here. A legitimate 'security researcher' would obtain his information by other means and discuss the subject via a secure channel with trusted participants - not anonymous strangers!
There are only two productive reasons to require this knowledge - security, and crime; idle curiosity is not a reason - do something more interesting and useful with your time.
Just accept that you are in the wrong forum, no one here wants to discuss the subject with you.
Clifford
The MinGW compiler is not a CLR compiler, so we are talking about native machine code rather than 'byte code'.
Although the GDB debugger can disassemble code I don't think the rather mediocre Dev-C++ GUI interface to it supports in in any wat that would be useful (you can access the GDB command line directly).
A better alternative would be to use the Insight debugger, It has source, source+assembler, and assembler display modes and you can step at the line or instruction level. You can download Insighr for MinGW at www.mingw.org. You can integrate it with Dev-C++ using the tools menu customisation feature.
If you just want an assembler listing of the code, that is possible without a debugger (although not straightforward): http://sourceforge.net/forum/forum.php?thread_id=1379841&forum_id=48211
Clifford
Thanks Clifford brother,
I had add in the insight debugger,now i can view the machine code,but...by default it is view as AT&T format,is it possible view the code in INTEL format??
Wait for ur reply...:)
But what are u going to do after taking the source code..???
Unfortunately I don't think GDB will display Intel format.
Given that it is unlikely that you will be staring at large swathes of generated code is that really a problem? A primer of the differences between AT&T and Intel is at http://www.w00w00.org/files/articles/att-vs-intel.txt
You could use the objdump utility to disassemble to either syntax and use that as a cross reference. The generation of assembler listings during compilatrion as described in teh earlier link can also be nade to produce Intel syntax I believe - check the GAS documentation: http://www.gnu.org/software/binutils/manual/gas-2.9.1/
Clifford
Hi All,
1)Actually it still have problem,it just show the disassemble code but no byte code come out.
2)For the INTEL or AT&T format i think is find,i will read the article regarding the differences.
3)Actually i'm learning to create shellcode(for exploit purpose).
4)I can get the byte code in visual c++,but it just a trial version,it need license so that's why i choose other compiler,may be someone can tell me any free compiler that can get the byte code while disassemble the program in windows base OS.
LTC
I was about to answer all your remaining questions until I read (3), so now you can go to hell. The less you know about programming the better.
Clifford
Stop calling it "byte code"! How many times does than need saying?
"learning exploit" is "still programming", but it is programming malicious code - I don't have to assist the a**holes who consider that acceptable. Most people involved in criminal activity usually have the good sense to keep quiet about it - you have continued to enjoy support then!
Clifford