• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2136
  • Last Modified:

ignoring "first chance exceptions" in delphi debugger

I'm coding an app that commicates with a database, partly through messages sent from a stored proc in the DB.
When the app is run from windows, everything works fine, but when I run it from the debugger, the trouble starts as soon as it receives a message from the DB and replies to it.
Delphi stops execution at this point, and shows an error window titled "Debugger fault notification", where it says "Project xxx faulted with message: "system exception (code 0xc0000008) at 0x7c90eb74'.  Process stopped.  Use step or run to continue."
I've googled the error codes, and found some stuff on first chance exceptions, meaning the exception is handled succesfully by the app  (in  this case a third-party dll responsible for the message handling) but when debugging it halts execution.   It has something to do with the handle of the message object not being handled correctly.  But I have no influence over this because this stuff is done inside a dll of wich I have only the interface, not the source code.

Now I would like to know how to determine exactly wich exception this is, so I can tell delphi to ignore it, in the debugger options.
Sometimes delphi offers the possibility to ignore this kind of exception", but in this case it does not.   It's a real pain that the debugger pops up everytime my app gets a message, so I would really like to turn this off.  
Any ideas?
0
DirkVerdonck
Asked:
DirkVerdonck
  • 2
1 Solution
 
jimyXCommented:
In Delphi IDE:

Go to "Tools" then "Debugger Options" from "Language Exceptions" un-check "Stop on Delphi Exceptions"
0
 
DirkVerdonckAuthor Commented:
found the solution myself.  Sorry jimyX, I've tried what you suggested but that didn't work.

this is how I did it:
tools - options and then debugger options - borland debuggers - native OS exceptions
there I've added an exception class ranging from 0xc0000008 to 0xc0000008, and specified it should be handled by the user program, and on resume "run handled".
Next time I ran the application I got a different error message specifying an exception of "exception class 0xc0000008" had occured, giving me the option to in the future ignore this class of exceptions.
I chose the ignore option and resumed execution.
next time I tried running the app from the debugger everything worked perfectly.
0
 
DirkVerdonckAuthor Commented:
I've been trying different things with the debugger options for two days now, I've finally found it.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now