Catch exceptions in a windows-DLL writte in C

Question

0.00/5 (No votes)

See more:

Greetings!

I've ported a C-module from linux shared object to windows DLL.
All works fine except that signal trapping I'm using with linux-c apparently does not work in a windows DLL.

I tried SetUnhandledExceptionFilter() but this also does not work within a DLL.

Any hints?

Posted 7-Feb-15 0:43am

WolfG1

Add a Solution

Comments

Richard MacCutchan 7-Feb-15 7:20am

You should not be setting that in the DLL. Library functions should perform services and return a status (success or fail), or (possibly) throw an exception. Exceptions should be caught and handled in your application code, so you can properly dispose of them.

WolfG1 8-Feb-15 7:55am

Tru, but the app is not my code.
Furthermore, I need some post motrtem info from the DLL (stacks, etc.)

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Frankie-C · Accepted Answer · 2015-02-07T02:21:00

SetUnhandledExceptionFilter don't work because the it will trap only exceptions that have no other handler.
Because the runtime already set the catching of all execptions for housekeeping duties you will get no trapping in your code.
It is also not wise to use in shuch DLL's that could be unloaded (like that user loaded or removable) because in this case if the library is no more in memory the handler will still refer to the address set previously resulting a call in unexistent code.
Using same care when coding a DLL, maybe you can use AddVectoredExceptionHandler().
For usage sample see here.