debugging

Provides a "Log" function that outputs a string to a debugging console, which is DCon on Mac and something like DebugView on Windows. This allows you to add instructions to your code and see them on the text logged by an RB-independent tool, allowing you to even see whats going when your RB app should crash right after the output.

You can use Debugging Tools for Windows to easily debug drivers, applications and services on systems running Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and Windows Server codename "Longhorn," as well as for debugging the OS itself.

Versions of the Debugging Tools for Windows package are available for 32-bit x86, native Intel Itanium and native x64 platforms.

The 64-bit versions of Debugging Tools for Windows allow you to debug both 32-bit and 64-bit user-mode applications running on 64-bit processors. Use this package to debug both the application and the WOW64 emulator.

Debugging Tools description
You can use Debugging Tools for Windows to debug drivers, applications and services You can use Debugging Tools for Windows to easily debug drivers, applications and services on systems running Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and Windows Server codename "Longhorn," as well as for debugging the OS itself.

Debugging Tools for Windows package is available in two versions: for 32-bit x86, native Intel Itanium and native x64 platforms.

The 64-bit versions of Debugging Tools for Windows allow you to debug both 32-bit and 64-bit user-mode applications running on 64-bit processors. Use this package to debug both the application and the WOW64 emulator.

Requirements:

· Microsoft Internet Explorer 5.0 or later.
· Approximately 25 MB of hard disk space.

Libcwd is a full-featured and well-documented library that assists C++ developers with debugging their applications.

C++ Debugging Support library includes support for ostream-based debug output, custom debug channels and devices, memory allocation debugging, run-time sourcefile:linenumber information, and demangled type names of variables. It is thread-safe.

Here are some key features of "Cplusplus Debugging Support library":

· End-users of an application dont need to install libcwd.
· The use of namespaces prevents name collisions between debug channels of different libraries.
· Debug channels and devices can be turned on or off on a per thread basis.
· All debug code can be omitted from the executable by not defining a single CWDEBUG macro.
· Code using libcwd looks clean and is surveyable as a result of using a few well-defined macros, avoiding the need of disturbing #ifdef CWDEBUG ... #endif constructs.
· Debug output is written to an ostream and as such type-safe and customizable as is usual for C++ ostreams.
· An arbitrary number of debug channels and debug devices can be created without any penalty in terms of cpu usage.
· Full support for all forms of iterative and recursive calls.
· Debug output is surveyable as a result of several possibilities to format the output, like a margin string, a marker string, indentation and fixed-width channel labels. All formatting is thread specific.
· Printing the type of arbitrary variables in demangled form.
· Printing addresses in source file:line number presentation.
· Deallocation pointer validation.
· Magic numbers around allocated memory blocks in order to detect buffer overruns.
· Printing an overview of current memory allocations, including start address, size, type of allocated object, source file and line number of allocation and a user definable description.
· Finding allocation information with only a pointer that points inside an allocated memory block, in logarithmic time.

Whats New in This Release:

· This release adds support for x86_64.

NoBug debugging library is a simple debugging library (only a single nobug.h header) similar to gnu-nana and Design-by-Contract ideas.

Here are some key features of "NoBug debugging library":

· Three different levels for checks (in depth to final no-overhead)
· Scope tags (tell whenever a function or loop is considered to be bug free)
· Pre-, Postcondition and Invariant checks, generic Assertions
· Debugger support (actions are only executed while running under a debugger), currently only valgrind
· Dumping of your datastructures
· Logging your applications activities
· Runtime customizable logging via an enviromnet variable
· Different logging targets (stderr, syslog, debugger...)
· Annotation of your sourcecode about known bugs, things to do and planned things

Whats New in 0.2 Stable Release:

· The source code location handling (file/line/function) was improved and centralized.
· Logging flags in C++ applications can be initialized and parsed with a simple initializer.
· The Resource Registry was stabilized and rewritten and given a new interface.
· Resources can be acquired in three states.
· Multithreading support for the Resource Registry was improved.
· All actions on the Resource Registry can emit logging messages.
· Only a few fixes were made since the 0.2rc1 release.

Whats New in 0.3pre1 Development Release:

· A deadlock detector was added. This is a review release, a work in progress.

HateML Pro Remote Debugging Extension description
Firefox add-on that will turn on or off the Remote Debugging in your webpage HateML Pro Remote Debugging Extension will easily turn on or off Remote Debugging in your browser.

Requirements:

· Firefox: 1.5 2.0.0.

Charles is an HTTP proxy / Reverse Proxy / HTTP monitor that enables a developer to view all of the HTTP traffic between their machine and the Internet. This includes requests, responses and the HTTP headers (which contain the cookies and caching information).

Charles can act as a man-in-the-middle for HTTP/SSL communication, enabling you to debug the content of your HTTPS sessions.

Charles simulates modem speeds by effectively throttling your bandwidth and introducing latency, so that you can experience an entire website as a modem user might (bandwidth simulator).

Charles is especially useful for Macromedia Flash developers as you can view the contents of LoadVariables, LoadMovie and XML loads. More about Charles and Flash.

Charles is also useful for XML development in web browsers, such as AJAX (Asynchronous Javascript and XML) and XMLHTTP, as it enables you to see the actual XML that is flowing between the client and the server.

Here are some key features of "Charles Web Debugging Proxy":

· Cookies are shown in the HTTP headers, so you can see exactly what cookies you are sending and receiving.
· Every request and response is recorded in Charles. Redirects that are often too quick to see when testing with a web browser can be seen in Charles. Requests from applications other than your web browser (such as Flash movies) can also be seen.
· Request and response sizes are shown in Charles, so you can see how big each request was.
· Assets loaded from an HTML page are recorded so that you can see how many images etc are loaded by a page, and where from.
· All files can be viewed, including JavaScript files, CSS files, HTML files etc.
· Mirror all responses to disk, recording your session.
· Blacklist sites so that requests are blocked.
· See the results of caching by seeing cached responses (304 Not Modified), and requests containing last modified dates (IfModifiedSince).
· Disable caching by removing cache related headers from requests and responses as they pass through Charles, ensuring that you are always requesting the latest file.
· See whether a cache has served your request by looking for cache-hit HTTP headers.
· View encrypted HTTPS traffic in plain text. Enables you to view requests and responses in plain text even when communicating with an SSL secured web server.
· Reveal unexpected requests, such as typos and 404s.
· View requested images.
· Bandwidth Throttle your web connection to a specified bytes/second speed, and millisecond latency. This enables you to simulate modem conditions on a high speed internet connection (bandwidth simulator)
· Spoof DNS name to ip mappings so that you can test a domain name before it has gone live. Very useful for testing your virtual hosting.
· Export to CSV all of the summary data captured by Charles for analysis and reporting in Excel
· Reverse proxy creates ports on the localhost that act as regular HTTP servers, but forward all requests to a specified web server.
· HTTP 1.1 support - including keep-alive, chunking and content-encodings including gzip, compress and deflate.
· External proxy support - configure an proxy for Charles to use to access the Internet
· NTLM authentication support (Windows NT Challenge Response Authentication / Integrated Windows Authentication)
· Automatic configuration of Windows Internet Proxy settings.
· Search all headers and bodies for keywords.
· Port forwarding support, allows any protocol to be forwarded by Charles and debugged.
· Unicode and other charset encoding/decoding support.
· AJAX debugging (Asynchronous Javascript and XML) and XMLHTTP debugging
· AMF parsing to help debug Flash Remoting
· Firefox proxy autoconfiguration
· Automatic Update Checking

Charles is an HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP traffic between their machine and the Internet. This includes requests, responses and the HTTP headers (which contain the cookies and caching information).

Charles can act as a man-in-the-middle for HTTP/SSL communication, enabling you to debug the content of your HTTPS sessions.

Charles simulates modem speeds by effectively throttling your bandwidth and introducing latency, so that you can experience an entire website as a modem user might (bandwidth simulator).

Charles is especially useful for Macromedia Flash developers as you can view the contents of LoadVariables, LoadMovie and XML loads. More about Charles and Flash.

Here are some key features of "Charles Web Debugging Tool":

· Cookies are shown in the HTTP headers, so you can see exactly what cookies you are sending and receiving.
· Every request and response is recorded in Charles. Redirects that are often too quick to see when testing with a web browser can be seen in Charles. Requests from applications other than your web browser (such as Flash movies) can also be seen.
· Request and response sizes are shown in Charles, so you can see how big each request was.
· Assets loaded from an HTML page are recorded so that you can see how many images etc are loaded by a page, and where from.
· All files can be viewed, including JavaScript files, CSS files, HTML files etc.
· Mirror all responses to disk, recording your session.
· Blacklist sites so that requests are blocked.
· See the results of caching by seeing cached responses (304 Not Modified), and requests containing last modified dates (IfModifiedSince).
· Disable caching by removing cache related headers from requests and responses as they pass through Charles, ensuring that you are always requesting the latest file.
· See whether a cache has served your request by looking for cache-hit HTTP headers.
· View encrypted HTTPS/SSL data.
· View encrypted HTTPS traffic in plain text. Enables you to view requests and responses in plain text even when communicating with an SSL secured web server.
· Reveal unexpected requests, such as typos and 404s.
· View requested images.
· Throttle your web connection to a specified bytes/second speed, and millisecond latency. This enables you to simulate modem conditions on a high speed internet connection (bandwidth simulator)
· Spoof DNS name to ip mappings so that you can test a domain name before it has gone live. Very useful for testing your virtual hosting.
· Export to CSV all of the summary data captured by Charles for analysis and reporting in Excel
· Reverse proxy creates ports on the localhost that act as regular HTTP servers, but forward all requests to a specified web server.
· HTTP/1.1 support - including keep-alive, chunking and content-encodings including gzip, compress and deflate.
· External proxy support - configure an proxy for Charles to use to access the Internet
· NTLM authentication support (Windows NT Challenge Response Authentication / Integrated Windows Authentication)
· Automatic configuration of Windows Internet Proxy settings.
· Search all headers and bodies for keywords.
· Transparent forwarding support, allows any protocol to be forwarded by Charles and debugged.
· Unicode and other charset encoding/decoding support.

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.

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...

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!

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.