vbscript debug

Debug is an assembly debugger for the Palm OS Emulator, and Simulator. It communicates using the Palm Debugger Protocol. Its a Java application, so it works in all OS environments that support the JVM.

Here are some key features of "Debug":

· The disassembler generates more descriptive opcodes. You see your code the way you wrote it.
· Innovative features, easy to use commands.
· Window gives you a view of the entire procedure unassembled, buttons to navigate forward or backward to the next procedure and a convenient Set Breakpoint button for setting both Trap breaks and regular Breakpoints.
· Support for Palm OS 4.0 SysTraps
· Along with the disassembly of the instruction, it also displays the contents of source variables! You can see what\s being loaded!

A frustration in debugging in Access 2000 and later is the clunky rigmarole required to check/set error-trapping.

Youll have the opportunity to simplify the process. Ezy Debug is launched from the right-click popup menu in the code window of the Access VB Editor.

The applet provides quick access to the Access error-trapping settings in the code window, and once invoked it is available both in the Access Database and VBE window.

The current error-trapping setting is displayed and can be hanged on the fly...

GW Debug is a simple debugging application for Win32 software. It can be used in conjunction with the debug version of the DirectX SDK in order to trace DirectX calls made by the program.

Debug::FaultAutoBT is a Perl module for automatic backtrace extractor on SIGSEGV, SIGBUS, etc.

SYNOPSIS

use Debug::FaultAutoBT;

use File::Spec::Functions;
my $tmp_dir = File::Spec::Functions::tmpdir;

my $trace = Debug::FaultAutoBT->new(
dir => "$tmp_dir",
#verbose => 1,
#exec_path => /home/stas/perl/bin/perl,
#core_path_base => catfile($tmp_dir, "mycore"),
#command_path => catfile($tmp_dir, "my-gdb-command"),
#debugger => "gdb",
);

# enable the sighandler
$trace->ready();

# or simply:
Debug::FaultAutoBT->new(dir => "$tmp_dir")->ready;

When a signal, that normally causes a coredump, is delivered This module attempts to automatically extract a backtrace, rather than letting the core file be dumped. This has the following benefits:

no need to setup the environment to allow core file dumped. Sometimes people just dont know how to set it up. Sometimes you arent allowed to set it up (e.g., when the webserver environment is not under your control).

if many Perl programs are run in a row and more than one program segfaults its possible to collect all backtraces, rathen then aborting the run on the first segfault or staying with only the last core file, which will overwrite all the previous ones. For example consider a live webserver or a test suite which may segfault many times for different reasons.

for huge core files, this approach saves disk space. And can be a saver when you dont have disk space left for various reasons (passed the quota?), but still have a few kilo-bytes left.

Currently the following signals are trapped:

SIGQUIT
SIGILL
SIGTRAP
SIGABRT
SIGEMT
SIGFPE
SIGBUS
SIGSEGV
SIGSYS

(If you know of other signals that should be trapped let me know. thanks.)

Debug::Message is a Perl module that eases the use of debug print with level, indentation and color.

SYNOPSIS

use Debug::Message;
use Log::Dispatch;
use Log::Dispatch::Screen;

my $dispatcher = Log::Dispatch->new;
$dispatcher->add( Log::Dispatch::Screen->new( name => screen,
min_level => 0 ));

my $info = Debug::Message->new(1);
$info->add_dispatcher($dispatcher);
$info->print("print");
$info->yellow("warn");
$info->red("err");
$info->printcn("error message", bold red);

my $critical = Debug::Message->new(5);
$critical->add_dispatcher($dispatcher);
$critical->redn("err");
For disabling the debugging simply do not attach any dispatchers.
$critical->disable; # Will detach the attached backend

There was no module for simple debug messages supporting debug/verbosity levels and indentation. So this is the one, that is supposed to take this place.
This module is an art of frontend to Log::Dispatch as Log::Dispatch itself supports levels, but no colors and the functions calling is tedious.

There are some methods defined. Each outputs a different color, optionally it can add a newline after the messaage. They dispatch the messages to all added dispatchers, but generaly only one will be needed as the Log::Dispatch itself can have more backends.

Debug::Phases is a Perl module to announce BEGIN and INIT phases to help locate problems.

SYNOPSIS

use Debug::Phases;

# Your code here


or:

> perl -MDebug::Phases your_script

This tiny module does nothing but announce the start of the BEGIN and INIT phases, recording how long the compilation (BEGIN phase) took. Its handy for tracking down whether particular problems are compile-time or run-time, and also for evaluating the time-cost for using other modules.

INTERFACE

None. It simply prints its information to STDERR.

DIAGNOSTICS

Compiling...

Your script is currently in its BEGIN phase

Compiling...%s seconds. Running...

Your script just finished its compile phase (in the indicated time) and is now executing.

Debug::Trace is a Perl extension to trace subroutine calls.

SYNOPSIS

perl -MDebug::Trace=foo,bar yourprogram.pl

Debug::Trace instruments subroutines to provide tracing information upon every call and return.

Using Debug::Trace does not require any changes to your sources. Most often, it will be used from the command line:

perl -MDebug::Trace=foo,bar yourprogram.pl

This will have your subroutines foo() and bar() printing call and return information.

Subroutine names may be fully qualified to denote subroutines in other packages than the default main::.

By default, the trace information is output using the standard warn() function.

MODIFIERS

Modifiers can be inserted in the list of subroutines to change the default behavior of this module. All modifiers can be used in three ways:

:name to enable a specific feature.
:noname to disable a specific feature.
:name(value) to set a feature to a specific value. In general, :name is equivalent to :name(1), while :noname corresponds to :name(0).

The following modifiers are recognized:

:warn

Uses warn() to produce the trace output (default). :nowarn Sends trace output directly to STDERR.

:caller

Add basic call information to the trace message, including from where the routine was called, and by whom. This is enabled by default.

:stacktrace

Add a stack trace (call history).

:maxlen(length)

Truncate the length of the lines of trace information to length characters.

The following modifiers can be used to control the way Data::Dumper prints the values of parameters and return values. See also Data::Dumper.

:indent

Controls the style of indentation. It can be set to 0, 1, 2 or 3. Style 0 spews output without any newlines, indentation, or spaces between list items. :indent(0) is the default.

:useqq

When enabled, uses double quotes for representing string values. Whitespace other than space will be represented as [ntr], "unsafe" characters will be backslashed, and unprintable characters will be output as quoted octal integers. This is the default, use :nouseqq to disable.

:maxdepth(depth)

Can be set to a positive integer that specifies the depth beyond which which we dont print structure contents. The default is 2, which means one level of array/hashes in argument lists and return values is expanded. If you use :nomaxdepth or :maxdepth(0), nested structures are fully expanded.

:quotekeys

Controls wether hash keys are always printed quoted. The default is :noquotekeys.

sortkeys

Controls whether hash keys are dumped in sorted order. The default is :nosortkeys.

Modifiers apply only to the subroutines that follow in the list of arguments.

Auto Debug for Windows is an auto-tracing application of programs.

User can set breakpoints, this application will auto trace the target program and record the input and output of function call.

Therefore, the software can help programmer analysis errors, process inside the target program, especially help the programmer analysis the sequences and parameters of the function call.

Debug agent is the Auto Debug Professionals Agent. Its a remote debug agent. Debug Agent is a simple Auto Debug software, it can load a config file and auto run the target application, auto recorder application trace, and auto save the trace to file.

So that you can debug your application on your custom PC. You can know what had happened on your customers PC and fixed your application bugs.

Here are some key features of "Auto Debug Professional":

· Automatic analysis parameter type with pdb files. Support for Visual Studio 2005, Visual Studio .NET 2003 and Visual C++ 6.0.
· Very easy generate pdb files without source code if you know the api prototype.
· Tracing your application with release version.
· The best API monitor tool.
· Tracing Release version with mapfile.
· Supporting debug version and release version, not need source code.
· Supporting tracing COM Interface.
· Supporting multithread.
· Not need to know the prototype of the functions.
· Not only trace for exported APIs, but also be effect for undocumented APIs.


Limitations:

· nag screen

Auto Debug for Windows is an auto-tracing application of programs.

User can set breakpoints, this application will auto trace the target program and record the input and output of function call.

Therefore, the software can help programmer analysis errors, process inside the target program, especially help the programmer analysis the sequences and parameters of the function call.

Debug agent is the Auto Debug Professionals Agent. Its a remote debug agent. Debug Agent is a simple Auto Debug software, it can load a config file and auto run the target application, auto recorder application trace, and auto save the trace to file.

So that you can debug your application on your custom PC. You can know what had happened on your customers PC and fixed your application bugs.

Here are some key features of "Auto Debug Professional":

· Automatic analysis parameter type with pdb files. Support for Visual Studio 2005, Visual Studio .NET 2003 and Visual C++ 6.0.
· Very easy generate pdb files without source code if you know the api prototype.
· Tracing your application with release version.
· The best API monitor tool.
· Tracing Release version with mapfile.
· Supporting debug version and release version, not need source code.
· Supporting tracing COM Interface.
· Supporting multithread.
· Not need to know the prototype of the functions.
· Not only trace for exported APIs, but also be effect for undocumented APIs.


Limitations:

· Nag screen

SWF Debug Remover description
SWF Debug Remover will allow you to delete enabledebuger(enabledebuger2) tags from files of any versions of the SWF Flash format SWF Debug Remover will enable you to erase enabledebuger(enabledebuger2) tags from files of any versions of the SWF Flash format.

The program has a built-in player of SWF-files. SWF Protect Debug can work with the packed SWF-files and pack them after processing.

The program is simple in utilization, all the actions are carried out by means of click on the corresponding button on the panel of tools.

Here are some key features of "SWF Debug Remover":

· deletion of the enabedebugger (enabedebugger2) tags;
· reproduction of the initial and processed file;
· rewind of the video;
· actions with the video;
· zoom in/zoom out the size of the videoimage;
· adjustment of its size to the size of a window
· the maximal filling of a window with the videoimage
· removal of the screen picture

Auto Debug for Windows is an auto-tracing utility of programs.

User can set breakpoints, this application will auto trace the target program and record the input and output of function call.

Therefore, the software can help programmer analysis errors, process inside the target program, especially help the programmer analysis the sequences and parameters of the function call.

Here are some key features of "Auto Debug for Net":

· Support VB.NET, C#, and all managed programs.
· Recording input parameters and return value of the methods which are set breakpoints in the target program. Therefore, not need to compile the source code, you can monitor the input and return value of methods.
· Supporting debug version and release version, not need source code.
· Supporting multithread. Through displaying sequence chart, easy get sequence relationship between all the threads.
· Support attach process feature. Its not only to trace application but also can tracing WebService.

Auto Debug application is an api monitor tool which can automatic tracing all apis and activex interface input and output parameters.

Easy set which api want to monitor, this application will auto trace the target program and monitor the input and output of function call. Monitor any dll and activex interface, automatic analysis pdb files.

Unlike others apispy or api monitor tools, Auto Debug software did not need user to develop any dll or hook dll. Its so easy.

Only set the apis which we want to monitor checkbox to ON, once the target application to running and called these apis, it will monitor these apis input and output parameters with automitatic!

Didnt need to develop any dll, once installed the software, we can start to monitor apis NOW!

Here are some key features of "Auto Debug for x64":

· Automatic analysis parameter type with pdb files.(new in V4.0). Support for Visual Studio 2005, Visual Studio .NET 2003 and Visual C++ 6.0.
· Very easy generate pdb files without source code if you know the api prototype
· Tracing your application with release version.
· The best API monitor tool.
· Tracing Release version with mapfile.
· Supporting debug version and release version, not need source code.
· Supporting tracing COM Interface.
· Supporting multithread.
· Not need to know the prototype of the functions.
· Not only trace for exported APIs, but also be effect for undocumented APIs.

The Debug Diagnostic Tool (DebugDiag) is designed to assist in troubleshooting issues such as slow performance, hangs, memory fragmentation or leaks, and crashes in any Win32 user-mode process.

The Debug Diagnostic Tool includes additional debugging scripts focused on Internet Information Services (IIS) applications, web data access components, COM+ and related Microsoft technologies.

DebugDiag 1.0 was released as part of the IIS Diagnostic toolkit and as a standalone tool. DebugDiag 1.1 is currently available as a standalone tool.

DebugDiag provides an extensible object model in the form of COM objects and provides a script host with a built-in reporting framework.

It is composed of the following 3 components; a debugging service, a debugger host, and the user interface.

The Debugging Service
The debugger service (DbgSvc.exe) performs the following tasks:
- Attach/Detach the host to processes
- Collect performance monitor data
- Implement HTTP ping to detect hangs
- Inject leak monitor in running processes
- Collect debugging session state information
- Shows the state of each rule defined

The Debugger Host
The Debugger Host (DbgHost.exe) hosts the Windows Symbolic Debugger Engine (dbgeng.dll) to attach to processes and generate memory dumps. It also hosts the main analyzer module to analyze memory dumps. Dbghost.exe has no dependency on the service DbgSvc.exe and can be used separately.

The User Interface
The user interfaces (DebugDiag.exe and DebugDiagAnalysisOnly.exe) present an interface to analyze memory dumps, automate the creation of control scripts and show the status of running processes, including services.
It is composed of 3 views:
- Rules: Creates control script for the debugger host through a wizard. The script is located under scripts
- Advanced Analysis: Runs a selected Analysis Script against one or more memory dumps.
- Processes: Shows status of running processes/services