-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unstable catching #3
Comments
case 3 (died):
Not sure why it died as i have demo app and it works perfect (catches exception every time). Now i'm trying with production code and it does not catch exceptions. i've checked everything few times and i'm in stuck. Any thoughts? |
I don't see any crash in the logs - this is most probably unrelated to coffeecatch. Do you have a simple reproducible test case ? (Note that crashes are not exceptions, but signals - coffeecatch won't catch any C++ exceptions, if this is what you are looking for.) |
according to the code above (writing to NULL pointer) signal 11 is sent and it's not catched by coffeecatch (cases 2,3) but sometimes it is catched (case 1). i've created demo app (issue 2) and coffeetaches does catch such errors all the time. i expect coffeecatch to catch it and throw java exception in this app too but the app just dies. if i comment the code above it's working good. so should coffeecatch handle such errors? |
i've moved native lib from my example project (https://github.com/4ntoine/CoffeeCatchDemo) to production project and it does not catch signals at all. It must be environment or other libs affecting this or smth. Any thoughts? I can't provide production code source but I can check any code or your thoughts as i like your lib and i want to make it working in production code. Please contact me using email dev [at] antonsmirnov [dot] name or skype anton.smirnov.skype or please leave your contact (email, skype). |
Sorry, but unfortunately I don't have the time for that. If you are using other native libraries, first run your code without using them (without loading them at all, to prevent any static initializers) |
Ok, no problem. But i don't think the issue is resolved just because you don't time to resolve it. |
I can't understand and this can probably be not coffeecatch issue, but it seems to be.
Sometimes crash is not catched and the process just die:
case 1 (catched):
case 2 (died):
the code:
The text was updated successfully, but these errors were encountered: