-
Notifications
You must be signed in to change notification settings - Fork 8
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
Signal handlers #28
Comments
Signals are consumed internally not to crash the app. Maybe I need to redirect it to user code? |
what do you mean by user code?, and is there a way to set a function to happen at exit() without it interfering with any other already existing atexit handlers that may already be set up, and if possible make sure it is always called either first, or last, depending on what the atexit handlers do if they exist, preferably id want it to be called after all handlers unless one happens to call exit or equivilant cpp*/crr* exit function |
nvm i thought u meant user code as in like u have some kind of user code for all the signals lol |
would i be correct at assuming by usercode you mean, for example, when exit() or abort() is called, or any other error such as manually stopping the program via stop or back button, or anything that would normally generate a signal of some kind, it would check for a signal hander for the signal that is being consumed internally and if one exists redirect it to that function for the apropriate signal? |
User is YOU here! |
If you give me signal handling example code, I can test and fix for it to work correctly. |
Look at the one in first post lol |
it should be able to catch every signal, if the signals are sent correctly, assuming all signals can be catched/intercepted/produced |
i will attempt to try to reproduce some of the signals if possible |
But it's not valid c code!! lol |
is there any way to get longjmp to work |
@dztall A rough file with all signals, not complete
|
What signal handlers are currently implimented/catchable, as exit(), abort() and others do not appear to generate a signal when called, as i can catch sig abort by freeing a invalid pointer, and segv by causing my program to intentionally seg fault, but i seem to be unable to catch any other signals, or at least dont know how to generate them
The text was updated successfully, but these errors were encountered: