Delphi 4.0x shareware
Debugging

[ adpack.zip ] [ 253,986 bytes ] [ Shareware ] [ No Source ]
[ D3 | D4 | D5 ]
ADP II Protection for Delphi
This is new anti-debugging & anti-monitors routines provide a good way to prevent *lame* people from spying your code. With ADP Component, you could protect your program from being cracked or spying without your permission. The main aspiration of ADP Component is to make the crackers meet more difficulty to crack your program. ADP Protection have some especial code to defeat most Debuggers and Monitors as W32Dasm, SoftIce, TRW 2000, Turbo Debugger, Sourcer, Filemon, ExeSpy, ResSpy, RegMon, Memory Monitor, Procdump.
Added: 16-04-2000   |  Version: n/a   |  Downloads: 1374/1374/3
Author:Bruno Branciforti   [Homepage]   [DSP files]

[ ej-trial.exe ] [ 2,881,130 bytes ] [ Shareware ] [ No Source ]
[ D1 | D2 | D3 | D4 | D5 | C1 | C3 | C4 ]
Event Journal from Fenestra Technologies provides a simple and automatic way to hook into and log all user-interface events (such as selecting menus, clicking buttons, minimizing windows, etc.) for any Borland Delphi or Borland C++ Builder application. Without Event Journal, software developers at best must make educated guesses on how their applications are being used in the field. With Event Journal, you are able to peer over your your user's shoulder as they use the application (see the online help for a note on privacy). Using the TFTEventJournal component is simple -- drop the component onto your existing application's main form, and all user-interface events are automatically logged with no further coding. The event journal provides the raw data you need to answer to such vexing questions as: What are the exact user-interface steps leading up to an unhandled exception? (Great for tracking down those pesky hard-to-reproduce problems!) How do users actually use my application in the field? What can I do to make my application easier to use? In addition to automatically logging user-interface events, the Event Journal also facilitates debugging your application. You can manually add debug strings to the journal by calling the LogUserMessage method, plus you can create your own custom events and plug them into the architecture. Event Journal includes an Event Viewer application that enables the you to browse, filter, export, and print the event journal. You can use the Event Journal only while beta testing, or you can leave it in your final application -- the choice is yours. You can even distribute the Event Viewer to the end-users of your software to assist in technical support.
Source included with registered version
Added: 7-09-2000   |  Version: 1.04a   |  Downloads: 881/881/0
Author:Fenestra Technologies Corporation   [Homepage]   [DSP files]

[ em151.zip ] [ 362,580 bytes ] [ Shareware ] [ No Source ]
[ D3 | D4 | D5 | C4 | C5 ]

What is ExceptionalMagic? Briefly, it's embedded debugging tool that provides some useful information about application's state at the moment of abnormal termination caused by exception. In contradistinction to well-known stupid message "Access violation in ... at ..." ExceptionalMagic informs about the exact location of error in application (source file name and line number) and also about a sequence of calls that leaded to this (so called callstack).

So, a brief list of main ExceptionalMagic features consists of:

  • exceptions catching and logging (both handled and unhandled)
  • localizing an error: finding module,procedure,source file and linenumber by address of error
  • callstack generating and logging
  • context (registers, stack, and code) logging
  • customizable error dialog box

It should be noticed that mechanisms of source code localization from an address and callstack tracing could be used any time and anywhere in application.

See what's new and what's fixed in 'History of changes' on ExceptionalMagic page on my site http://dimus.virtualave.net

Also you can download from my site pre-compiled MegaDemo application with Delphi5 sources. It demonstrates almost all features of ExceptionalMagic.

Added: 12-03-2000/14-05-2000   |  Version: 1.51   |  Downloads: 1659/1623/2
Author:Dimus Gremyakoff   [Homepage]   [DSP files]

[ excmagic.zip ] [ 113,291 bytes ] [ Shareware ] [ No Source ]
[ D3 | D4 | D5 ]
This unit replaces standard exception handling behaviour with much more controlled and informative one. It allows you to customize many aspects of exception handling and provides a lot of useful info and features:
  • location of exception in source (file name & line number)
  • call-stack information (module name & proc name)
  • contents of CPU registers and stack
  • custom formatting of error message
  • custom displaying of error message
  • write exception information into log file
Added: 17-10-1999   |  Version: 1.1   |  Downloads: 1623/1623/2
Author:Dimus Gremyakoff   [Homepage]   [DSP files]

[ watchdog.zip ] [ 117,986 bytes ] [ Shareware ] [ No Source ]
[ D3 | D4 | C3 | C4 ]
Central managment for monitoring and recording exceptions of application. Mainly usefull for debuging end user implementations. Also it can be used for detail monitoring exception appearance (include user name, date, time, class and name or exception source, text of message etc...). These records are writen to file (TXT and HTML format) or showed live in Watch (debug) window. Price: $25 without source, $40 with source.
Added: 15-06-1999   |  Version: 2.0   |  Downloads: 1560/1560/0
Author:L. Svoboda   FDsystem   [Homepage]   [DSP files]

© 1995-2006 Robert M. Czerwinski ( The Delphi Super Page a.k.a. DSP ).
All rights reserved.