Re: permissions (and other) problems

Jon Watte wrote:

>>>A slightly less kludgey fix is to install a SIGINT handler which
>>>does a longjmp() to some routine which cleans up all currently
>>>registered "cleanup" handlers. Typically, something that starts
>>>a transaction will register transaction rollback as a cleanup task,
>>>and something which opens the database will register database close
>>>as a cleanup task...
>>>
>>>
>
>
>
>>No. We want to be portable, and doing anythint except setting a
>>sig_atomic_t global variable from within a signal handler is not portable.
>>
>>
>
>While that is probably true, the benefit of using the signal handler
>approach is that you can also catch SIGSEGV to do the same clean-up :-)
>
There's also the small problem that longjmp'ing out of a signal handler
loses context, which means that we can't clean up the database locks
anyway -- defeating the purpose of this exercice.

And trying to clean up after a seg faulr simply doesn't work in general.

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org