flat assembler
Message board for the users of flat assembler.

Index > Windows > Debugging...

Author
Thread Post new topic Reply to topic
sgi1981



Joined: 04 Apr 2006
Posts: 2
Location: Ukraine, Kharkov
sgi1981
I use FASM 1.67.21.
The good assembler.
But the debugging of the programs is necessary. It is possible to do debugging in disassembler IDA PRO, but so it is inconvenient.
What you can give to me advice ?

_________________
Everywhere and always there should be a physical reality and there should be a common sense
Post 09 Mar 2007, 15:22
View user's profile Send private message Reply with quote
okasvi



Joined: 18 Aug 2005
Posts: 382
Location: Finland
okasvi
For user-mode debugging I suggest OllyDbg.
Post 09 Mar 2007, 15:33
View user's profile Send private message MSN Messenger Reply with quote
HyperVista



Joined: 18 Apr 2005
Posts: 691
Location: Virginia, USA
HyperVista
yes, i agree with okasvi. ollydbg is very good and very free of cost! Very Happy
http://www.ollydbg.de/
Post 09 Mar 2007, 21:00
View user's profile Send private message Visit poster's website Reply with quote
Garthower



Joined: 21 Apr 2006
Posts: 158
Location: Ukraine
Garthower
I use FDBG. It's good and free debugger. I can find for more information at: http://board.flatassembler.net/topic.php?t=5045
Post 09 Mar 2007, 23:48
View user's profile Send private message Visit poster's website MSN Messenger ICQ Number Reply with quote
ACP



Joined: 23 Sep 2006
Posts: 204
ACP
Olly is great - especially if you use it's plugins and code analysis options - but it will only handle ring 3 code. For ring 0 use WinDBG:

http://www.microsoft.com/whdc/devtools/debugging/debugstart.mspx

IDA Pro also has ring 3 debugger that supports Windows/Linux targets and remote debugging. When using WinDBG make sure you have symbol server properly configured.
Post 11 Mar 2007, 23:22
View user's profile Send private message Reply with quote
r22



Joined: 27 Dec 2004
Posts: 805
r22
Incremental developement is the best way to avoid having to debug stuff.

Make and test every procedure one at a time and if your code breaks you'll always know where to look (the last thing you didn't test). Of course there is always that case where you just can't find the problem and a debugger (OR massive amounts of printf/messagebox calls) is needed.

Another good way to avoid spending hours in a debugger is use algorithms that you've already tested in a HLL (or even in other asm projects). You can throw something together pretty fast in say java or vb test it out make sure it works then write it in assembly and you'll have a good working base to start optimizing it.

-off topic - does FDBG still go into the kernel APIs while debugging? I remember an old version I used for win xp64 did that and it was so annoying having to step through the windows apis to get back to my code. Maybe there was an option to turn it off but I was just ignorant of it.
Post 12 Mar 2007, 05:29
View user's profile Send private message AIM Address Yahoo Messenger Reply with quote
vid
Verbosity in development


Joined: 05 Sep 2003
Posts: 7105
Location: Slovakia
vid
Quote:
Incremental developement is the best way to avoid having to debug stuff.

Make and test every procedure one at a time and if your code breaks you'll always know where to look (the last thing you didn't test). Of course there is always that case where you just can't find the problem and a debugger (OR massive amounts of printf/messagebox calls) is needed.

r22: only in theory. You can't realize every possible state of function. Some functions can have 100 or more specific cases... impossible to find and try every one yourself.

Quote:
Another good way to avoid spending hours in a debugger is use algorithms that you've already tested in a HLL (or even in other asm projects). You can throw something together pretty fast in say java or vb test it out make sure it works then write it in assembly and you'll have a good working base to start optimizing it.

writing it directly in asm and testing it there is IMHO easier than writing it in HLL and rewriting to asm

Quote:
-off topic - does FDBG still go into the kernel APIs while debugging? I remember an old version I used for win xp64 did that and it was so annoying having to step through the windows apis to get back to my code. Maybe there was an option to turn it off but I was just ignorant of it.
I think last time i tried it, there was "step into" and "step over" like in every debugger
Post 12 Mar 2007, 09:50
View user's profile Send private message Visit poster's website AIM Address MSN Messenger ICQ Number Reply with quote
Display posts from previous:
Post new topic Reply to topic

Jump to:  


< Last Thread | Next Thread >
Forum Rules:
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Copyright © 1999-2020, Tomasz Grysztar. Also on YouTube, Twitter.

Website powered by rwasa.