Sorry, I have been kind swanped latelly, I didn't have any time to reply to your previous email, although I read it.
Why couldn't we just say that this function, is to use in some special cases, in my case I need because I don't want an error handling function being capable of calling ERR_clear_errors, et erase my error stack, before I had time to send it back to the user. However, the ERR_set_mark and ERR_pop_to_mark do not "disable" ERR_clear_errors, and it's something that I need to have in my project. If you don't feel like implementing it, why don't we really enable custom error handling functions? Since it's has been kind of implemented already, then I could do what I want without annoying everyone with my silly requests. Frédéric Giudicelli http://www.newpki.org ----- Original Message ----- From: "Richard Levitte via RT" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, June 20, 2003 12:20 AM Subject: [openssl.org #629] Custom error handling > > Just for the sake of keeping history with this ticket: I've concerns > with ERR_disable() in relation to the OpenSSL code checking for certain > errors in some places. If error setting is disabled, we might very well > end up with unwanted problems. Sure, it can be fixed by temporarely > re-enabling error setting, but that requires an extra effort from > OpenSSL developpers, and this is easily forgotten. > > [levitte - Wed Jun 11 22:55:38 2003]: > > > I've implemented ERR_set_mark() and ERR_pop_to_mark(), which can be > > used > > for similar functionality. I'll look into ERR_disable() and > > ERR_enable() as well, but that requires quite a lot more work. > > > > If the implemented functions are enough for you for now, I'll resolve > > this ticket. > > > > [EMAIL PROTECTED] - Mon May 26 09:16:48 2003]: > > > > > Hi, > > > I would like to implement some kind of error locking function: > > > > > > SYSerr(x,x); > > > ERR_disable(); //We don't want anymore error feedback from this > > point > > > //call to functions that can potentialy generate some more errors > > > ERR_enable(); //Re-enable error feedback > > > > > > In this exemple the last error will be the one generated by > > > "SYSerr(x,x);". > > > > > > I tried to implement a custom error handling function, > > > int_thread_get_item equivalent that would return NULL, if the > > > thread error handling was locked, but any call to > > > ERR_clear_error destroyed the "SYSerr(x,x);" error. > > > > > > The custom error handling doesn't seem to be really supported > > (ERR_FNS > > > is opaque..., etc), altough the bases are there, could it be > > > possible to either fully support custom error handling, or to add > > > the ERR_enable/ERR_disable. > > > > > > Thanks, > > > Frédéric Giudicelli > > > http://www.newpki.org > > > > > > > > -- > Richard Levitte > [EMAIL PROTECTED] > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
