PARD: Development
Checker is a debugging tool suite which find memory errors at runtime. It's
like a GNU 'Purify'. It still has alpha status and you need gcc version
2.8.1 to use Checker. It currently works only for C, yet. (C++ was not
tested).
Code Medic is a graphical debugger that provides access to the power of gdb
with an intuitive front end. It currently supports opening multiple source
windows at once, setting/clearing breakpoints while the program is running,
watching variables change in the variable tree as you step through code
(even with nested structs), text searching through source, and integration
with Code Crusader to provide a rapid, efficient develop-debug cycle.
The Data Display Debugger (DDD) is a common graphical user interface for
command-line debuggers as GDB, DBX, XDB, JDB, the Python debugger, or the
Perl debugger. Besides ``classical'' front-end features such as viewing
source texts, DDD provides a graphical data display, where data
structures are displayed as graphs. A simple mouse click dereferences
pointers or views structure contents, updated each time the program stops.
Using DDD, you can reason about your application by viewing its data, not
just by viewing it execute lines of source code.
Electric Fence is a different kind of malloc() debugger. It
uses the virtual memory hardware of your system to detect when software
overruns the boundaries of a malloc() buffer. It will also
detect any accesses of memory that has been released by free().
Because it uses the VM hardware for detection, Electric Fence stops your
program on the first instruction that causes a bounds violation. It's then
trivial to use a debugger to display the offending statement.
| Modified | 05 March 1998 22:30
|
GDB, the GNU debugger, allows you to debug programs written in C, C++, and
other languages, by executing them in a controlled fashion, printing their
data, etc.
wxWindows/GTK aka wxGTK is a GTK port of the cross-platform wxWindows C++
class library.
Xterminal is an Object Oriented User Interface with a client-server
architecture. The main purpose is a friendly interface for the UNIX-like
operating systems. It is designed to be used to build text-based
applications in C++.
It consists of a complete object oriented library including multiple,
resizeable, overlapping windows, pull-down menus, dialog boxes, buttons,
scroll bars, input lines, check boxes, radio buttons, etc. Mouse support,
advanced object management, events handling, communications between objects
are provided, too, bundled with a complete programmer's manual.
gIDE is a gtk-based Integrated Development Environment for C. The
development has just started, but gIDE already features a powerful editor
with syntax highlighting. gIDE is currently in heavy development and help
will always be appreciated.
WipeOut is an integrated software development environment for C, C++, Java
and Fortran projects. It contains a project browser, revision browser, text
editor, class browser, make tool, symbol retriever, debugger, and a help
browser. It's available for Linux/i486/Alpha/m68k, Solaris/Intel/Sparc and
HP-UX.
The gettext library provides an easy to use library and tools for creating,
using, and modifying natural language catalogs. It is a powerful and simple
method for internationalizing programs. Supported languages (in messages):
da, de, es, fr, nl, no, no@nynorsk, ko, pl, pt, sl, sv.
| Current version | 0.10.35
|
| Modified | 07 January 1999 10:59
|
This is a perl5 module quickly written to gain access to the C library
functions for internationalization. They work just like the C versions.
Installfest provides an attractive environment for configuration,
compilation and installation.
InstallFest is a program that combines 3 functions, of which each is
optional:
- Configuring the program
- InstallFest guides the user through
configuration of the application, if necessary, and passes the parameters to
./configure - Providing progress of the compilation process
- InstallFest provides the user with a status of the compilation in forms
of a progressbar.
- Information about the program by means of slides during
the compilation
- Slides can be shown to the user during compilation,
highlighting new features and other information.
However, a program with installfest support, doesn't require the users to
have InstallFest installed, neither does it obligate users (and developers)
to use it. In fact, the addition of InstallFest happens with no difference
in the installation/compilation process to who chooses not to use
InstallFest, and with only a very slight change for the developers.
Autoconf is a tool for producing shell scripts that automatically configure
software source code packages to adapt to many kinds of UNIX-like systems.
The configuration scripts produced by Autoconf are independent of Autoconf
when they are run, so their users do not need to have Autoconf.
The configuration scripts produced by Autoconf require no manual user
intervention when run; they do not normally even need an argument specifying
the system type. Instead, they test for the presence of each feature that
the software package they are for might need individually. (Before each
check, they print a one-line message stating what they are checking for, so
the user doesn't get too bored while waiting for the script to finish.) As a
result, they deal well with systems that are hybrids or customized from the
more common UNIX variants. There is no need to maintain files that list the
features supported by each release of each variant of UNIX.
For each software package that Autoconf is used with, it creates a
configuration script from a template file that lists the system features
that the package needs or can use. After the shell code to recognize and
respond to a system feature has been written, Autoconf allows it to be
shared by many software packages that can use (or need) that feature. If it
later turns out that the shell code needs adjustment for some reason, it
needs to be changed in only one place; all of the configuration scripts can
be regenerated automatically to take advantage of the updated code.
| Modified | 05 March 1998 22:43
|
© 1999 by Stefan Hornburg
<racke@linuxia.de>
Last modified 03. June 1999