Newsdetails

I'm pleased to announce the release of Exceptq v7.1 and MapXQS v1.0.
With just 5 lines of code, developers can add Exceptq's comprehensive trap
reporting facility to their apps. If the app encounters a fatal exception,
Exceptq will generate a report containing: the call stack, disassembly of
the faulting instructions, a stack dump, a listing of dlls loaded into the
process, and more.

Exceptq v7.1 offers these new features:

* Support for symbol files in the new XQS format. .XQS files have none of
the size limitations of .SYM files, include module info for each symbol,
and are extensible. MapXQS, included in the package, will create them
from mapfiles generated by IBM, GCC, OpenWatcom, and Borland linkers.

* The non-fatal EXCEPTQ_DEBUG_EXCEPTION lets developers generate Exceptq
reports at any point in their program's execution. Additional debugging
data can be passed to the handler for inclusion in the report.

* Support for an application-provided string containing version or build
information that will appear at the top of the report.

* Better identification of addresses contained in registers, and new system
info such as total memory, virtual address limit, and processor count.

The developer's edition containing how-to information and needed files is
available from:
hobbes.nmsu.edu/h-search.php
or
e-vertise.com/misc/exceptq71-dev.zip

A user's edition with just dlls and installation info can be had from:
hobbes.nmsu.edu/h-search.php
or
e-vertise.com/misc/exceptq71.zip

If you have an app that uses an earlier version of Exceptq, please upgrade
to v7.1.

For more information, please contact:
Rich Walsh <rich*e-vertise*com>
or
Steven Levine <steve53*earthlink*net>