Release date: 
Sunday, 8 July, 2018



Exceptq adds a comprehensive trap reporting facility to your app with just 5 lines of code. Reports include: the call stack, disassembly of the faulting instructions, a stack dump, a listing of dlls loaded, and more. The zip contains how-to info and needed files, including the new MapXQS.exe.

Programs that include this special debugging technique must always be distributed with the corresponding files of symbols (.sym/.xqs) or debug (.dbg) ones, for each executable module, otherwise the information from any exceptions, being incomplete, are not very useful to developers.

This software is distributed in two modes:
  • as compressed package that you have to download and manually install; if prerequisites are required, you will have to manually install them too;
  • as RPM package; you can install it using your favorite rpm package manager, that will take care to download and install both the software and its prerequisites.
Choose the installation mode that you prefer. Please note that not all the versions are available in both the installation modes.

Installation with rpm

This program is installable using the rpm package manager. See below for the install string. Required prerequisites are automatically processed by the package manager and, if needed, downloaded and installed.

exceptq-7.11.3 (01/08/2016)
Repository: Netlabs stable
____________________________________________________________________________ ____________________________________________________________________________ Readme for Exceptq v7.1 Portions of Exceptq are Copyright (c) 2000-2010 Steven Levine and Associates, Inc. Copyright (c) 2010-2011 Richard L Walsh The remainder of Exceptq is Copyright (c) 1992-2000 Marc Fiammante et al. ____________________________________________________________________________ Contents ____________________________________________________________________________ * Overview * Options * Installation * Files ____________________________________________________________________________ Overview ____________________________________________________________________________ Exceptq v7.1 creates a debugging report whenever a program that uses it encounters a fatal exception (i.e. the app crashes). Programmers can also use it to generate debugging reports while the app is running. It emits a two-tone beep, then generates the report and puts it in the directory containing the .exe that crashed. The name is based on the IDs of the process and thread that encountered the problem. For example, '006C_01.TRP' describes a trap in process 6C, thread 1. Reports are typically 10-30k - small enough that it should be easy to email them to the program's author, even on dialup. Most of the info they contain is of little value to the user. However, you may want to examine the last section, "DLLs accessible from this process", to see if a dll was loaded from an incorrect or unexpected directory. If you have any questions about Exceptq v7.1 - or any problems with it, please contact: Rich Walsh <rich@e-vertise.com> or Steven Levine <steve53@earthlink.net> ____________________________________________________________________________ Options ____________________________________________________________________________ Exceptq v7.1 offers several options that can be controlled by setting the environment variable "EXCEPTQ"; the options are not case-sensitive. Beeps ----- The beep is intended to remind you that there's an exception report available that you can send to the program's author. If it bothers you, add "SET EXCEPTQ=Q" to config.sys. B "beep" [default] Q "quiet" Generate Report --------------- Use this to disable Exceptq for a particular program while leaving it available for other apps. You may need this if an app is so unstable that the reports are more of an annoyance than a help. This option should be added to a .cmd file used to start the app, not config.sys. Y "yes" [default] N "no" Generate Debugging Report ------------------------- Developers can include code that forces Exceptq to create a report while the program is running without having to wait for a crash. This feature is normally disabled but a developer may ask you to enable it using this option. D "debug & fatal exceptions" F "fatal exceptions only" [default] ____________________________________________________________________________ Installation ____________________________________________________________________________ Installation is simple: copy the two dlls and the xqs file to a directory on your LIBPATH so that all apps that use Exceptq share the same files. If you have copies of older versions of Exceptq, please remove them (users of MR2I and FM/2 may have copies in those directories). Apps designed to work with earlier versions will work better with v7.1 (it's much faster) while new apps that expect v7.x will be unable to use those older versions. ____________________________________________________________________________ Files ____________________________________________________________________________ The users' distribution of Exceptq v7.1 (exceptq71.zip) contains these files: exceptq.dll the exception handler dll exceptq.xqs exceptq's public symbols distorm.dll the disassember used by exceptq distorm.xqs distrom's public symbols readme.exceptq this file A developers' distribution (exceptq71-dev.zip) containing files and info needed to add Exceptq support to an application is also available. ____________________________________________________________________________ Rich Walsh <rich@e-vertise.com> March 1, 2011 ____________________________________________________________________________
exceptq-devel-7.11.3 (01/08/2016)
Repository: Netlabs stable (note: development files, not needed by the end user)
Tue Jul 05 18:24:58 2016 Steven H. Levine <steve53@earthlink.net> * exceptq.dll v7.11.3-shl Report process date, time and size Release v7.11.3-shl

Manual installation

Available both as ZIP and WarpIN package:

  • download the ZIP package to temporary directory and unpack it to destination folder, better if in PATH;
  • the WarpIN package is self-installing.

See below for download link(s).

Following ones are the download links for manual installation:

ExceptQ v. 7.11.5b8 (1/6/2020, Steven Levine) Readme/What's new
Mon Jun 01 18:09:58 2020 Steven H. Levine * exceptq.dll v7.11.5-shl BETA8 Rework WalkStack to better handle return from 16-bit to 32-bit code Add more memory access checks to WalkStack
ExceptQ v. 7.11.5b7 (19/5/2020, Steven Levine) Readme/What's new
Tue May 19 15:01:49 2020 Steven H. Levine * exceptq.dll v7.11.5-shl BETA7 Enhance Z option. Z no longer reports for XCPT_ASYNC_PROCESS_TERMINATE. ZZ does. Rework XCPT_PROCESS_TERMINATE in DLL memory access checking.
ExceptQ v. 7.11.5b3 (15/5/2020, Steven Levine) Readme/What's new
Fri May 15 13:33:54 2020 Steven H. Levine * exceptq.dll v7.11.5-shl BETA3 Enable code to correct distorm decode address range logic
ExceptQ v. 7.11.5b2 (23/4/2020, Steven Levine) Readme/What's new
Thu Apr 23 20:18:24 2020 Steven H. Levine * exceptq.dll v7.11.5-shl BETA2 Search for .xqs files before .sym files Report DLLs loaded in high-memory Report address and size of loaded DLLs (1st code object only) Report OS2KRNL timestamp and size Avoid intermittent trap in WalkStack for thunked stacks Correct distorm decode address range logic Rework copydbg to have more generic error messages Some folks were confused by the CodeView references
ExceptQ v. 7.11.5b1 (8/7/2018, Steven Levine) Readme/What's new
Sun Jul 08 10:50:03 2018 Steven H. Levine * exceptq.dll v7.11.5-shl Show errno if .trp file open fails Release v7.11.5-shl
ExceptQ v. 7.11.4 (WarpIn package by Doug Bisset, 31/3/2017, Steven Levine) Readme/What's new
Mon Mar 06 17:29:39 2017 Steven H. Levine * exceptq.dll v7.11.4-shl Correct FPU status word IE status formatting Release v7.11.4-shl
ExceptQ v. 7.11.3 (WarpIn package by Doug Bisset, 27/7/2016, Steven Levine)
ExceptQ v. 7.1 (3/1/2011)
Record updated last time on: 28/03/2021 - 12:36

Translate to...

Add new comment