Index
> Linux > Another debugger questionn. |
| Author |
|
|
a16b03 01 Jun 2006, 16:59
Is there any TurboDebuger like debuger for linux?
|
|||
01 Jun 2006, 16:59 |
|
|
rugxulo 06 Jun 2006, 02:45
|
|||
|
06 Jun 2006, 02:45 |
|
|
stanks 07 Jun 2006, 04:21
Try insight (if you are using GUI
 ). It is frontend for gdb. |
|||
|
07 Jun 2006, 04:21 |
|
|
rank amateur 15 Jul 2006, 03:12
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?
|
|||
|
15 Jul 2006, 03:12 |
|
|
UCM 15 Jul 2006, 15:31
Unfortunately, FASM is incapable of generating debug symbols.
|
|||
|
15 Jul 2006, 15:31 |
|
|
rank amateur 15 Jul 2006, 15:39
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?
|
|||
|
15 Jul 2006, 15:39 |
|
|
vid 15 Jul 2006, 16:40
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. |
|||
|
15 Jul 2006, 16:40 |
|
|
Reverend 15 Jul 2006, 21:24
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.
|
|||
|
15 Jul 2006, 21:24 |
|
|
rank amateur 16 Jul 2006, 00:48
Isn't OllyDbg a windows-only debugger?
|
|||
|
16 Jul 2006, 00:48 |
|
|
UCM 16 Jul 2006, 13:30
rank amateur wrote: Isn't OllyDbg a windows-only debugger? Yeah, it is. _________________ This calls for... Ultra CRUNCHY Man! Ta da!! *crunch* |
|||
|
16 Jul 2006, 13:30 |
|
|
Reverend 16 Jul 2006, 17:06
 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. |
|||
|
16 Jul 2006, 17:06 |
|
|
rank amateur 16 Jul 2006, 18:52
No worries. Just wanted to be sure I didn't overlook something.
|
|||
|
16 Jul 2006, 18:52 |
|
|
Endre 17 Jul 2006, 11:08
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. |
|||
|
17 Jul 2006, 11:08 |
|
|
rank amateur 18 Jul 2006, 13:39
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.
|
|||
|
18 Jul 2006, 13:39 |
|
|
Posetf 24 Jul 2006, 01:46
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? |
|||
|
24 Jul 2006, 01:46 |
|
< Last Thread | Next Thread > |
Forum Rules:
|