Is there any TurboDebuger like debuger for linux?

there isn't any debugger so good like Turbo Debugger

there is gdb but I don't like it because it uses different asm syntax
there are GUI apps like xgdb, ?kgdb (check the name please) still using different asm syntax
fortunatelly, there is ALD for 32-bit i386 using FASM friendly syntax, but is command line based as gdb
I develop fdbg for Linux 64-bit AMD64 using FASM friendly syntax, but is command line based as gdb
I don't plane to make it like TD, fdbg for Linux 64-bit AMD64 will stay command line based
I suppose that author of ALD doesn't plane to make it like TD too and it will stay command line-based

http://sourceforge.net/projects/rhide
http://sourceforge.net/project/showfiles.php?group_id=32142

Try insight (if you are using GUI ). It is frontend for gdb.

I'm completely new to fasm: have read the manual, but can't find any info on generating debugging symbols for linux debuggers. Can anyone enlighten me?

Unfortunately, FASM is incapable of generating debug symbols.

Okay, thanks for the reply. Can you tell me how one uses fasm effectively, if debugging info is not available? Being a noob at writing ia32 assembly, I tend to make a lot of mistakes, and tracking them down w/o a debugger would be a nightmare. Do fasm users instrument their own programs with a lot of extra code for debugging purposes, or do they write programs using other assemblers, then translate to fasm compatible format, hopefully w/o introducing errors in the process, when satisfied their code is error free?

good question - as beginner you may have problem with this. Debugging symbols usually help to find only stupid errors (using wrong variable or procedure), and later you have it "in hand" and stop making such errors. You named it right - "mistakes", FASM is like other VIM, or Unix, it's harder to use from beginning, but when you know it, it is better

surely you don't need to mix any language with FASM, like you suggested.

I use OllyDbg very often when coding in fasm. There are no debug informations, but the feature of assembly language is one-to-one compilation. The code you see in debugger is the same you wrote in editor. Of course there's no labels, variable names, etc. but it's still your code, so you should quickly know what's going on.

Isn't OllyDbg a windows-only debugger?

Yeah, it is.

My fault. I didn't notice it's "Linux" section. Sorry. But still my post generally about debuggers is true, only the text about OllyDbg should not be here.

No worries. Just wanted to be sure I didn't overlook something.

As you noticed fasm doesn't generate debug info, but you can live without it. Try e.g. ald: http://ald.sourceforge.net/.

Or you can use "as" (the gnu assembler) instead of fasm and then you get everything (debug symbols) you just need for debugging with gdb. With fasm you can also use gdb, but in a bit tricky way.

I'm satisfied with both kdbg and insight as debuggers, but am not enamoured with gnu assembler syntax, so I was looking for something better. Hence my interest in fasm which, apart from its lack of ability to generate debugging info, appears to be a very sleek and powerful assembler.

Sorry for the late reply, and reference back to win/ollydbg...
I litter my code with such as this:
debug = 1
if debug
sqrt db "sqrt",0
end if
..
if debug
cmp eax,sqrt
end if

(obviously being careful re condition codes)
Shows up helpful in ollydbg, does it work in others?