Possible memory leak on `__ctrycatch_exception_message`

[Jamesits]

There are no way to tell if __ctrycatch_exception_message is hardcoded or allocated in runtime.

[Klevh]

You can do two things. One is more elegant for the user (the second one) and one is more elegant in your code :

• add an optional third parameter for throw macro, being the "free" function to be used on the string at the end of its life (like, the appearance of the finally)

• use the signal function on SEGFAULT signal and try to free it, then just set the signal function back to NULL

I think that it should be the user that should free it though, if the throw can be catch that is

[Klevh]

I can help, I am working on the same project ^^ ( https://github.com/Klevh/Exsee )