Here sources for debugger. It is written in pure FASM of course.
Usefull for win64 fasm coders in development of programs, in analysis of unknown executables, you can find some ideas in sources.

tthsqe completely rewrote GUI for Windows x64 version of fdbg and added support for AVX - version 0025
http://board.flatassembler.net/download.php?id=6409

Windows x64 - version 0024 (supports windows 8 and windows server 2012) - old GUI style and lacks disassembling AVX
http://board.flatassembler.net/download.php?id=6131

Linux x64 - version 0011
http://board.flatassembler.net/download.php?id=4756

UEFI x64 - version 0006
https://board.flatassembler.net/download.php?id=9013

feryno - make people know your debugger by name, give this thread name like FDBG - Win64 debugger or so...

Whooops, guys, the fdbg version from 1st post in this thread was old one! I wanted to attach version from 2006 april 02, but I made a mistake.
to Vid - thanx, I have changed thread name according to your suggestion

For don't waste a lot of time by serching where are new features that weren't in older versions - they are accessible by right click on ListView or right click on main win.

edit 2006-july-03
deleted attachment because 5 MB quota limit

Added some 'camouflage' options (I have never seen this in any debugger, but I had these ideas and I have transformed them into reality)

fdbg is able to:
- hide itself against IsDebuggerPresent
- hide itself against FindWindow (needs fdbg restart)
- camouflage TrapFlag (avoid to detect debugger by save TrapFlag by pushf)

You can test these features with included sample kick_out_dbg\a00.exe
Usefull for developing antidebugs or for break them, it depends on user...

edit 2006-july-03
deleted attachment because 5 MB quota limit

improved dialogs: rearranged positions of items, limittext where necessary
sorting of imported APIs when collumn clicking (ascendent only - alphabetical, memory addr)
corrected threads' mess when attach_process
fixed bug in EXECUTETO

edit 2006-july-03
deleted attachment because 5 MB quota limit

Hello Feryno,

Thanks a lot for your updates. I really like them.

You have done many improvements in the user interface and it's much better now, but it's still a bit tough to use. What I miss is the possibility to resize each window with the mouse (like we can do with any MDI application) and also to allow moving a specific window with the mouse.

I know it's easy to say but difficult to implement, but that feature will make a big difference for many people about using or not your debugger

Thanks a lot for this excellent x64 debugger, I'm sure that in a near future it will be preferred for most of the people instead of M$ WinDbg

Cheers mate!

Here debugger for assembler coders under Linux64 AMD64 platform.
Not so good as ms win64 fdbg, but basic functionality is done. What more was I able to do in 5-7 days and 40-50 hours of coding in FASM ?

some keywords for easy find it by searching:
Linux Linux64 64 bit 64-bit AMD64 EM64T flat assembler FASM debugger

edit 2006-july-07
deleted attachment because 5 MB quota limit

fdbg ver. 0008 for AMD64 win64
- fixed some bugs
- allowed direct editing by simple click on listview item and subitem (but not allowed to edit everything ! - e.g. in code listview isn't allowed edit other addresses except first because painful back disassembler reconstruction)
- moving listviews by left rat's paw, you have to hold shift key (prevention of unwanted moving - nothing move without shift, but holding shift, you can release left rat, then release shift and move only with mouse move without holding pressed anything) - some ugly array of holding and releasing, see !_news.txt for details

edit 2006-july-07
deleted attachment because 5 MB quota limit

what about win32?

fdbg for Linux 64-bit AMD64
now it has everything necessary for debugger to have
it is command line based, runs in console

To Vasilev Vjacheslav - I left 32-bit world about 1 year ago, so I wont port fdbg into win32. I admire Borland Turbo Debugger and I tried to write debugger for win64 AMD64 with functions that are in TD32.exe. So key shortcuts are similiar, only GUI differs, because TD32 runs in console mode. FDBG for win64 is window app, not console app.
I want to support new AMD64 platform, for speed-up progress and new technologies. A lot of people are staying in 32-bit OS even they have AMD64, that's a pitty. People having old good 32-bit CPUs (i386) can use a lot of debuggers - like td32, GoBug, OlyDbg, ...

edit 2006-july-07
deleted attachment because 5 MB quota limit

ok-ok, i just ask

Some small changes, works well under Vista Beta2 x64 - changed font size
added option for ignore exceptions in code (for debugging in case you installed exception handler in your app)

edit 2006-july-07
deleted attachment because 5 MB quota limit

latest fdbg for win64 and Linux64
fdbg for win64 is able to debug exception handler procedure (see !_news.txt)

Hello Feryno! I have to you some request about your debugger in the Windows-version. Whether it's possible to make in it the built in windows in the basic window resizeable? In particular, it concerns windows where commands are displayed. It is inconvenient to debug, when in a window the information but only a part, and not conveniently constantly to use scrollbars. It will be how much complex to add such code?

Yes, I am working on it hardly. I have rewriten the sources completely, made the debug loop completely new, improve multiprocess and multithreads support. The new GUI is almost finished now. Everything is based on Alorents idea - in MDI, so bigger comfort..., your setting are saved on exit and restored on start.
I am going to fix 1 disasm mistake in indexing mode with something like [r13+r12*2+04]
I am happy that I solved how to simulate that we are on instruction of SW breakpoint (INT03 = db 0CCh). It's not so easy as it looks, because exception_breakpoint is generated after executing int03, so instruction pointer is after int03 opcode.
I am happy that I solved how to do breakpoint temporal (will be removed after its first trigger) and permanent (will stay after its execution).
I am happy that I solved WM_DRAWITEM handling (finished last night) - so you see colored instruction on current instruction pointer, color on breakpoint... in fdbg000A color losts after moving another window over it...
I am going to add actions there (there are only Single step, Step over, Run now) and changing registers (you can't any reg change in fdbg000B yet) - it will be by directly clicking on register and enter value into rectangle. I am going to make better Terminate Debuggee routine. I am going to add deleting breakpoint.
What is finished now - GUI, open exectuble, Single Step, Step Over, Run, Set sw breakpoint, set hardware breakpoint, set font. Nothing more. The most of missing things will be simple copied from fdbg000A. The reason why I am posting incomplete fdbg000B here is only for you can test its new GUI
I hope to finish it until september 29 when my wife and I expect our first baby. But +- 2 weeks for baby birth is normal date...

edit from 20060929: deleted attachment

just for fun - to demonstrate FDBG is 64bit, not 16bit, you could call versions FDBG000000000000000B

... jokin

yeah, I thought about it months ago, but it is tooooo loooong

realy?

how about numbering by 8bit number then? after 256 you can overflow, like:

10.2.2008: FDBG v11111101 released
3.3.2008: FDBG v11111110 released
12.3.2008: FDBG v11111111 released
5.4.2008: FDBG v00000000 released

Cool project, I will check it out when I get around to installing a 64bit OS.

here is it, you can rearrange position, resize, minimize everything what you want (MDI child win, column in SysListView32), you can set font and its size, fixed bug when disassemble some opcode with SIB (like [r13+r12*2+04], ...)
Especialy comfortable is moving through code with pgup/pgdown, up/down arrow, left/right arrow, toggle breakpoint with F2 or execute here (F4),...
And there is a help...
I did manual and heavy style of coding which has risk of rsp dqword misalignment (but benefit by smaller and faster code), so testing under Vista RC1 is very appreciated (simple MessageBoxA crashes in Vista when rsp is misaligned). FDBG has its own exception handler, so it notifies you where it causes exception: exceptions in its image (somewhere in address between 100001000h-100002xxxh) - they shouldn't occur, exceptions in DLLs space like at addr 7xxxxxxxh or 7FFxxxxxxxxh shouldn't occur either - caused ususaly by stack dqword misalignment

Attaching to a process isn't implemented in this version yet, use fdbg000A if you need it. Weapons against antidebugs (Rambo menu) aren't implemented either, use fdbg000A if you need to fight... I plane to add them as soon as possible.
I plane to correct fdbg for linux - only to rewrite about 5 lines in fdisasm engine is enough, I didn't manage it the last night.