Announcing Immunity Debugger v1.0

After almost a year of intensive development and internal use, we are
pleased to announce the public release of Immunity Debugger v1.0.

When we started developing Immunity Debugger our main objective was to
combine the best of the commandline based and GUI based debugger worlds.
The commandline because most of us come from a UNIX background, and it
just ends up being more efficient than clicking your way around. The GUI
because we understand that we are visual beings that often can
grasp more from a single look at a graphical layout than from two days
of x/x-ing memory pages.

The third feature we required was full flexible access to the debugging
API,
the graphing engine, and the GUI API. Because having to Re-Compile
plugins is lame, we decided to make everything accessible from Python.
So we put everything together and developed something we feel very
comfortable using.

This means we ended up with a fully flexible and extendible Win32
debugger that has all of it's features, both debugging and graphical,
easily accessible from it's Python scripting engine.

And best of all, it's available for free. That's right, Immunity
Debugger is released for free, including free monthly updates.

Here's some cool features:

o The Python API ("Immlib/Lib reference" for full documentation)
o A full Python based graphing library
o Full debugger and GUI API access
o A flurry of cool example scripts such as:

- !heap A fully working heap dumping script (try the -d option!)
- !searchheap Searching the heap
- !hippie Trampoline hooks on RtlAllocateheap/RtlFreeHeap
- !modptr Dynamic search for function pointers in pages
- !findantidep Find address to bypass software DEP

o Writing your own scripts for your specific tasks is easy

Interested? Give Immunity Debugger a spin and download it from:
http://www.immunitysec.com/products-immdbg.shtml
or check: http://forum.immunityinc.com

For feedback or bug reports please contact support at immunityinc.com.

Happy debugging!

Thanks,
Team Immunity

PS: Yes, we will be implementing an interactive Python shell too.

Is it written in FASM?

Nop, maybe I post it on an incorrect Board?

Well, this section if for projects written in FASM.
You could have posted it on the heap.
But let's wait the moderator to move it.

Anyway your project looks very interesting for us ASM programmers.
Thanks for letting us know.

moved to main instead... i wait for more feedback about debugger itself

It seems just like ollydbg with a few plugins and some ads on the top.
I Still wonder if they got ollydbg's sources..

It does use the ollydbg sources, in fact i think they freely admitted it somewhere...can't find the link though.
I personally detest this perversion of our sacred olly, we already had ollyscript...with no ads or random unknown exceptions...

Ehtyar.

They stolen the sources?

BTW, I think the first post of this thread qualifies as spam.

PS: Perhaps they just patched the original OllyDbg executable?

This debugger sounds cool, but what's with the Phyton stuff?

Python scripting in a debugger? Interesting.

I'm been trying this debugger. Looks cool. It's like Ollydbg with python scripting and custom syntax highliting.

Yes, the purpose of "Main" is to address features or issues involving FASM, or the use of FASM, not debuggers or any other application written in some "high level" language. That was also the basis of the objection, I had expressed, a week or so ago, to including the discussion of the "frensh" dictionary, in Main. If the topic does not directly concern FASM, it does not belong in "Main". Some people work on a messy, cluttered desktop, with papers, magazines, books, music CDROM's, power supplies, soldering guns, paint, cookies, automobile spark plugs, stamps from around the world, model trains, volt-ohm meters, and yesterday's coffee cups all mixed together with this month's electric bills, credit card receipts and banana skins. Others have a clean desk. What can I say? Oh, let's see what vid's desk looks like:
Yup. old coffee cups and banana skins for sure.

Since I've just seen this debugger again when following a not yet proven Firefox 3.6 vulnerability, I researched this a little. Although I didn't find the official voices (Oleh and/or ImmunityInc's site), looks that Oleh actually provides parts of the source for an old version here, and seems he offers/offered the complete source if you pay for it. I must say that at that time, my real thought was that they went through the effort of PATCHING the public OllyDbg binary rather than using the sources.

Copyright violations conspiracy apart, anyone here is using it?

I just use Olly to debug my stuff. I just insert an "int3" in a problem spot, compile and run. I find I don't need all the fancy pants scripting and stuff. Once I find the mistake I fix my source and carry on with things.

I think only people with interests in cracking or hacking have a need to use all the scripting and automated whatnot.

Not all reverse engineering has to do with cracking or hacking

I concur, not everyone using scritping and automation are cracking and hacking. I have several older items I have lost the source to, which I use (try to) a debugger(s) to get to that old information.

Too bad I can't take a picture right now, but it's relatively clean right now (compared to normal state). Just one empty beer glass, two beer cans, empty glass from pickles, a flute, destroyed drumstick, 4 books, screwdriver, pen, keys, and small heap of papers... not that bad at all.

So, Tom, where'd you prefer to have this thread moved? Heap?