1

I am looking for code or options to disable a run time error. Instead showing that stupid message I just want a crash or to just continue. So in conclusion to do no show that message.

pnuts
  • 58,317
  • 11
  • 87
  • 139
user558126
  • 1,303
  • 3
  • 21
  • 42

1 Answers1

0

This question (or at least a very similar one) has been answered in Disable Microsoft Visual C Runtime Error

The errors need to be handled within your program to stop things going out of your control and the Microsoft dialog being displayed. The answer referred to explains how to capture these errors yourself. One way of implementing crash handling is to capture the minidumps for yourself, using something like CrashRpt into your software.

Community
  • 1
  • 1
Andy Simpson
  • 367
  • 2
  • 6
  • There isn't any method to avoid to show any kind of error. Preferable to be closed and not to show an error. – user558126 May 07 '12 at 01:04
  • Some errors cannot be suppressed (in recent versions of VC), but they only relate to possible security breaches - see the last post on [here](https://connect.microsoft.com/VisualStudio/feedback/details/101337/a-proposal-to-make-dr-watson-invocation-configurable). – Andy Simpson May 07 '12 at 02:06
  • but that is only a small subset of the possible errors. Do you see a specific run-time error message each time, or is this a general question ? – Andy Simpson May 07 '12 at 02:11
  • Do you have a try/catch handler at the top level of your program ? – Andy Simpson May 07 '12 at 02:12
  • I have a code, and it gives me an error, and with a Delphi auxilar software I am checking if the process is opened if not it will open it. So it is not a problem. The idea is to create to crash it automatically without showing any kind of staff on the screen. – user558126 May 07 '12 at 02:41
  • I made a try catch in the top level and it gaves the same stupid message. How i can block it to don't show me the messsages? – user558126 May 07 '12 at 02:51
  • Error gived by my software: Assertion failed: result.full () , file d:\opencv....include\ flann\kdtree_index.h, line 523 ... What should I do? – user558126 May 07 '12 at 03:05
  • If you compile the opencv source, and it really doesn't matter if that process stops just get the process to exit rather than asserting if !result.full(). What happens if you build it with a release configuration, so that asserts are not in effect ? I guess it may fail in an uglier, but different place. – Andy Simpson May 08 '12 at 01:11