Problem with Visual Studio Just-In-Time Debugger error from a Delphi App

rbuser

Occassionally I receive a Visual Studio Unhandled Win32 Exception error on
WinXP stations when printing reportbuilder reports from a Delphi
application. It is very intermittent and I have not yet been able to
reproduce it in a development environment. I have some general
Reportbuilder questions below that may help guide me on where to look next
to resolve this issue.

Version Info:
ReportBuilder 11.04
Delphi 2009

ONE POSSIBILITY: The issue may be being caused by PDF file creation out of
reportbuilder
QUESTION 1: When reportbuilder creates a PDF does it utilize adobe programs
in the background?
QUESTION 2, IF YES TO QUESTION 1: Are there any known issues with any
versions of adobe?

QUESTION 3:
Does the latest reportbuilder utilize the .net framework or java or anything
outside of the delphi application for any internal aspects when generating a
report?
POINT RELATED TO QUESTION 3: We have had issues in the past where it seemed
reportbuilder was somehow generating error messages that I could not trap
inside Delphi. I was concluding that I was missing something in my error
handling or I wasn't exactly understanding the events firing but is it
possible that Reportbuilder can be generating an error that Delphi does not
trap or that a debugger outsode of Delphi would trap first.

Thanks,
Peter.

nardmoseley

I recommend updating to RB 11.05, which contains a couple of fixes for
intermittent AV's reported by other customers. Often an intermittent AV is
caused by a memory corruption that occured somewhere in the application.
Using FastMM in debug mode or a tool such as AQTime is about the only way to
track down these types of errors.

You can try using the Application.OnException event or using an exception
handling/loggin add-on such as JCLDebug or MadExcept. Still with the cuase
of a memory corruption issue, the exception will not show you where the
error occurred, it will mislead you.

In Delphi if you call try..exception and then inside the block you have code
that shows a modal dialog (such as a modal preview, print, or cancel
dialog) - then the exception will not be trapped. This is dues to Windows
architecture or Delphi architecture - I cannot recall which.

ReportBuilder does not use adobe, .net or java.

Delphi and Visual Studio both have the ability to register themselves as the
machines JIT Debugger. There can be only one JIT Debugger registered for a
machine. Any app you run on your machine written in any language can cause
the JIT Debugger to launch.


--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com