I have an application that runs perfectly on my development machine.  When I install it and run it on my VMWare environment it immediately
crashes.  Both OSes are XP Pro.  My application does involve several OCXes and such, but the earlier version runs just fine on both systems and
both applications use the same OCXes.

The "Send error report" dialog pops up immediately after the first form shows.

Is there any way to debug or figure out is wrong on the machine in which it crashes?

David,

<< I have an application that runs perfectly on my development machine.
When I install it and run it on my VMWare environment it immediately
crashes.  Both OSes are XP Pro.  My application does involve several OCXes
and such, but the earlier version runs just fine on both systems and both
applications use the same OCXes.

The "Send error report" dialog pops up immediately after the first form
shows.

Is there any way to debug or figure out is wrong on the machine in which it
crashes? >>

The only way is:

1) Install an IDE on the target machine and debug it natively
2) Remotely debug the application (much harder)
3) Compile it with something like MadExcept and use that to trace the
exception

--
Tim Young
Elevate Software
www.elevatesoft.com

A stroke of genius using MadExcept.

I should have known better to think it was a bug in MY code.  

Turns out it was my copy protection.  A component called for an
environmental variable which didn't exist because I was testing an
executable that didn't create the variable.  I compiled with MadExcept and
it listed the component's name.

Of course, now I have to send $100 to buy MadExcept because it looks very
useful and actually reports needed information.

Thanks for the reply Tim.


On 2/13/09 2:20 PM, in article
B0D4B8FF-B658-40E0-A6F2-131B0485FA20@news.elevatesoft.com, "Tim Young
[Elevate Software]" <timyoung@elevatesoft.com> wrote:

> David,

> The only way is:
>
> 1) Install an IDE on the target machine and debug it natively
> 2) Remotely debug the application (much harder)
> 3) Compile it with something like MadExcept and use that to trace the
> exception