I am looking for advice on Linux debuggers if there are some who use Linux.

What do you use, etc ?

Thanks.

The only debugger I've used on Linux is gdb either directly on command line or via an IDE such as Eclipse CDT (there are other graphical front ends that run on top of gdb as well).

Thanks for the info.

Andy

[ Post removed by author. ]

It may sound a blasphemy here on this forum, but if you're using fasm instead of practically any other assemblers on Linux then you'll be in trouble. It is because fasm is unable to generate standard debug info (like e.g. DWARF2) which is necessary for debuggers. Of course in tricky ways you can debug your code even without debug info, but it's far from convenient.

So if you're about to write bigger assembly programs on Linux I advise to change to other assembler which can generate proper debug info. On Linux the host debugger is gdb, nothing else. Learn it.

Not debugging is not an option for sane people.

Excuse me.
Is there no use FDBG in "Projects and Ideas" forum?
http://board.flatassembler.net/topic.php?t=9689
Nobody use this?

[ Post removed by author. ]

No 32 bit versions of fdbg ?

I am looking to analyze a "rogue dll."

It was caught in the system32 directory masquerading as a system file.

Tip off was that it had no version info, a very recent file date, and had all file attributes set.

I would like to analyze it using a tool passively debugs it.

Thanks.

As for debugging being just a tool.

You don't have to use one. We won't call you a newbie either.

[ Post removed by author. ]

You might have better luck using a Windows debugger either in Windows (virtual machine maybe) or using wine on linux. As it's 32bit you'll have more options too, as there are more older analysis tools around.

When we learn programming at the university at for the first time, we didn't thaught how to use debugger. So we put print statements here and there while manually reading portions of the code. Then we ran the code and examined the output.

Sure, we then realized that debuggers make our jobs easier. But sometimes we are lazy. No wonder this primitive debugging technique is still being used.

Since the code was malicious, I did not want to examine it using Windows.

I was able to get Windows installed into a Virtual box.

Now I can safely dissect it without any harm to my system.

I submitted it to virustotal and they mis-identified it.

They list the names that other companies gave the malware, so I conclude that they all got it wrong.

Gotta go back to my bug hunting.

I do a lot of work without debuggers (not on Linux) in assembler (not on Intel).

If you have trace and dumps it's also fine. But not having anything? You can't be productive and you can't possibly write any serious code without tools like dumps, traces, and debuggers. Because you really need to verify that each section of code is doing exactly what you want and not that you just got lucky and it looks like everything worked.

On Linux netbeans is ok, at least you get a GUI for gdb.

@Fixit
Have you tried Evan's Debugger?

Ollydbg is very popular among among Windows folks, and I think that's the closest one available for Linux.

[ Post removed by author. ]

And why? Why don't you use a debugger?

In embedded world your method just does not work at all. For instance because there is no display to print out anything on. Or because you have to check/modify 200 registers of a SOC (System On a Chip) peripheral to figure out why your driver doesn't want to work. Sometimes such a task is very hard even with a well working debugger.

But if you're about to write a hobby operating system to your x86/amd64 processor then you will face the very similar problems I described above.

[ Post removed by author. ]

You might want to re read my post.

<Today debuggers are too sophisticated. And I doubt very much they will be <available in an emergency case (e.g.: my paranoid reasons).

Too sophisticated, hmmm.

I would recommend a counselor.
They can help you with your thinking patterns and help you feel more at peace.

Laterz.

It's like when you crash with your bicycle and you notice that somebody has seen it, and then you just say: "Hey, what do you see? I get off the bike like this" .

Ok, just kidding. The debugger running on the human hardware is very important and useful. Even if you learn your code by heart you can use this technique when your computer is just not around you.