Home page logo

bugtraq logo Bugtraq mailing list archives

Re: WinAppDbg 1.4 is out!
From: Mario Vilas <mvilas () gmail com>
Date: Wed, 25 Aug 2010 14:57:06 +0200

Basically it supports 64 bits Windows, has a few more features, and
comes with a crash analyzer. PyDbg on the other hand supports Mac OS
and is integrated to PaiMei. So both frameworks have their own

Also the programming API for PyDbg is much simpler (but still
powerful), but WinAppDbg's is more complete, documented, and object

So if I were you, I wouldn't rush to port all my already written code
to WinAppDbg :) but if you're about to code something new you might
want to give it a try!

On Tue, Aug 24, 2010 at 9:42 PM, Aleksandr Yampolskiy
<ayampolskiy () gilt com> wrote:
How is it different from pydbg?
Sent from my Blackberry handheld.

----- Original Message -----
From: Mario Vilas <mvilas () gmail com>
To: bugtraq () securityfocus com <bugtraq () securityfocus com>; full-disclosure () lists grok org uk 
<full-disclosure () lists grok org uk>; Python-Win32 List <python-win32 () python org>
Sent: Tue Aug 24 09:00:59 2010
Subject: WinAppDbg 1.4 is out!

What is WinAppDbg?

The WinAppDbg python module allows developers to quickly code instrumentation
scripts in Python under a Windows environment.

It uses ctypes to wrap many Win32 API calls related to debugging, and provides
an object-oriented abstraction layer to manipulate threads, libraries and
processes, attach your script as a debugger, trace execution, hook API calls,
handle events in your debugee and set breakpoints of different kinds (code,
hardware and memory). Additionally it has no native code at all, making it
easier to maintain or modify than other debuggers on Windows.

The intended audience are QA engineers and software security auditors wishing to
test / fuzz Windows applications with quickly coded Python scripts. Several
ready to use utilities are shipped and can be used for this purposes.

Current features also include disassembling x86 native code (using the open
source diStorm project, see http://ragestorm.net/distorm/), debugging multiple
processes simultaneously and produce a detailed log of application crashes,
useful for fuzzing and automated testing.

What's new in this version?

In a nutshell...

 * fully supports Python 2.4 through 2.7
 * fully supports Windows XP through Windows 7, 32 and 64 bit editions
 * crash report tool now supports MSSQL (requires pyodbc)
 * now supports downloading debugging symbols from Microsoft (thanks Neitsa!)
 * new tool: sehtest.py (Windows SEH buffer overflow jump address bruteforcer,
  inspired by the same tool by Nicolas Economou)
 * the tutorial is now available in chm and pdf formats
 * now with only one MSI installer for all supported Python versions
 * added support for diStorm 3 (falls back to the old version if not found)
 * now using cerealizer instead of pickle whenever possible
 * added new command to the command line debugger to show the SEH chain
 * a few more anti-anti-debug tricks were added, still more to go!
 * several improvements to the Window instrumentation classes
 * more code examples
 * more Win32 API wrappers
 * lots of miscellaneous improvements, more documentation and bugfixes as usual!

Entire changelog for all versions (slow!):


Where can I find WinAppDbg?

Project homepage:


Download links:

 Windows installer (32 bits)

 Windows installer (64 bits)

 Source code



 For download

HONEY: I want to… put some powder on my nose.
GEORGE: Martha, won’t you show her where we keep the euphemism?

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]