Work out what is causing error

  • Thread starter Thread starter Matthew Sutton
  • Start date Start date
M

Matthew Sutton

Hi everyone,

We have an application that is developed in Borland C++ by an external
developer to the company. The applciation runs on Windows XP & Windows 2000
Pro machines.

At the momment, every so often it causes a Windows error, where a error has
happened in the program that Windows needs to close. It does not give an
error code adn the developer says he cannot work out whats causing it and he
cannot trap it either.

I was just wondering if anyone else out there has come acorss this siutation
or knows of a way we can track down either what part of our code or what bit
windows casued the error and try and work it out.


All thoughts and ideas apprecaited.

MAtthew Sutton
 
Sounds like you need to hire a competant developer. To say that the
exception can't be caught and it doesn't give an error code screams of
incompetance.

That being said, tell your "developer" to look into structured exception
handling, as well as Dr. Watson and installing symbols.


{L}
 
Back
Top