Free to debug software for linux

The debug-mode is started by adding a ".debug" to filenames. This module will then print some information about the request, before forwarding to the originally requested file.

Cookies and form-elements for that page can be edited with two forms in the debug-output. Later, I added the feature to print also the file with the ".debug"-suffix, if it exists. That way, you can statically add self-requests with given form elements.

PBS::Debug is a Perl module with debugger support for PBS.

SYNOPSIS

use PBS::Debug ;

AddBreakpoint
(
hi
, DEPEND => 1
, PRE => 1
, ACTIONS =>
[
sub
{
PrintDebug "Hi there.n" ;
}
]
) ;

ActivateBreakpoints(hi) ;

This module defines subs that manipulate PBS breakpoints (explained in PBS reference manual).

sub PrintBanner: display a friendly message when run under the perl debugger sub EnableDebugger sub p_h: display a help within the perl debugger sub p_b_wizard: not implemented sub p_list sub p_tree pretty print a tree sub p_dependencies pretty print the dependencies of a node sub p_node pretty prints a node

sub AddBreakpoint add a PBS breakpoint sub RemoveBreakpoints remove one or more PBS breakpoint according to the name regex passed as argument sub ListBreakpoints list all the breakpoints defined within PBS sub ActivateBreakpoints activates one or more PBS breakpoints sub DeactivateBreakpoints does the opposite of the above sub

ActivatePerlDebugger activates wether a breakpoint (or breapoints) jumps to the perl debbugger sub DeactivatePerlDebugger does the opposite of the above

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.

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.

KDbg is a graphical user interface to gdb, the GNU debugger. kdbg project provides an intuitive interface for setting breakpoints, inspecting variables, and stepping through code.
KDbg requires KDE, the K Desktop Environment, but you can of course debug any program.
Main features:
- Inspection of variable values in a tree structure.
- Direct member: For certain compound data types the most important member values are displayed next to the variable name, so that it is not necessary to expand the subtree of that variable in order to see the member value. For example, you dont need to go into a variable of type QString if you want to see the string that the variable holds. (BTW, this is of course not hardcoded, but can be extended to new types.) KDbg can also display Qt 3s QString values, which are Unicode strings.
- Debugger at your finger tips: The basic debugger functions (step, next, run, finish, until, set/clear/enable/disable breakpoint) are bound to function keys F5 through F10. Quick and easy.
- Of course, lots of other basic functions: View source code, search text, set program arguments and environment variables, display arbitrary expressions. Everything you need to debug a program, eh!
- Debugging of core dumps, attaching to running processes is possible.
- Conditional breakpoints.
Enhancements:
- The appearance of the main window for first-time users was improved.
- Improve file handling when the srcdir != builddir.
- Show value popups for members of this.
- Allow the user to give redirections in the Program Arguments dialog.
- Minor bug fixes.

DBG is a a full-featured php debugger, an interactive tool that helps you debugging php scripts.
It works on a production and/or development WEB server and allows you debug your scripts locally or remotely, from an IDE or console.
Main features:
- native debugger. Works transparently, neither script nor PHP engine modifications required.
- server part (dbg module) runs on all platforms where PHP itself runs.
- works transparently across the global network as well as locally.
- JIT. When enabled can start debugging Just In Time of error occurs.
- supports back-tracking, e.g. displays a list of all procedures with their local variables, the current execution position reached from. Also you can watch local variables or function parameters in all active and nested scopes.
- certainly, you can execute script in the debugger step by step (step-in, step-out, step-over...), evaluate any valid php expressions or complex variables, modify values of any variables on the fly and create any new ones. Breakpoints can be conditional, they also may skip entered number of hits.
- has embedded profiler, so now its easy to find out a bottleneck in the scripts.
- allows multiple debugger processes running simultaneously.
- compatible with php-4.0.6 and higher.
- has open COM interfaces for integration with win32-based 3rd party IDEs.
- Commercial version of DBG (2.16.x) is available with commercial version of PHPEd PHP IDE only, see review for details.
- Linux, BSD, SunOs, MacOs and Win32 platoforms are supported.
- Free version (2.11.x) is available on this site. It works with PHP Edit, PHP Coder and some other IDEs.
- Free dbg front-end (dbg-cli) for Linux/Unix can be used to debug scripts either directly or under DDD 3.3.9 (GNU debugger). Also see RedHat 7.3, YellowDog and Mandrake distributions at RPM Find site.
Enhancements:
- All php versions from 4.0.6 up to 4.3.10 and from 5.0.0 up to 5.0.3 are supported.
- Support for HARDENED php v0.2.6 added (4.3.9h, 4.3.10h and 5.0.3h).
- Command line interface (dbg-cli) improved.
- Tested with php 4.0.6, 4.1.0-4.1.2, 4.2.0-4.2.3, 4.3.0-4.3.10, 5.0.0-5.0.3.

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.
Main features:
- 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.

POE::Component::DebugShell is a component to allow interactive peeking into a running POE application.

SYNOPSIS

use POE::Component::DebugShell;

POE::Component::DebugShell->spawn();

This component allows for interactive peeking into a running POE application.

spawn() creates a ReadLine enabled shell equipped with various debug commands. The following commands are available.

COMMANDS

show_sessions

debug> show_sessions
* 3 [ session 3 (POE::Component::DebugShell controller) ]
* 2 [ session 2 (PIE, PIE2) ]

Show a list of all sessions in the system. The output format is in the form of loggable session ids.

session_stats

debug> session_stats 2
Statistics for Session 2
Events coming from: 1
Events going to: 1

Display various statistics for a given session. Provide one session id as a parameter.

list_aliases

debug> list_aliases 2
Alias list for session 2
* PIE
* PIE2

List aliases for a given session id. Provide one session id as a parameter.

queue_dump

debug> queue_dump
Event Queue:
* ID: 738 - Index: 0
Priority: 1078459009.06715
Event: _sigchld_poll
* ID: 704 - Index: 1
Priority: 1078459012.42691
Event: ping

Dump the contents of the event queue. Add a -v parameter to get verbose output.

help

debug> help
The following commands are available:
...

Display help about available commands.

status

debug> status
This is POE::Component::DebugShell v1.14
running inside examples/foo.perl.
This console spawned at Thu Mar 4 22:51:51 2004.
There are 3 known sessions (including the kernel).

General shell status.

reload

debug> reload
Reloading...

Reload the shell

exit

debug> exit
Exiting...

Exit the shell