On Thu, Nov 26, 2009 at 6:52 AM, Hermann Himmelbauer <dusty@qwer.tk> wrote:
If this bug did indeed exist in 3.4.1, we can backport the fix and do a 3.4.x bug-fix release.
Thanks a lot for help, that would really great. The question is, how do I find out (with my limited knowledge of zope.security) if the bug exists in 3.4.1?
From looking at the code, it seems the bug does exist in 3.4.1 (and 3.4.2). I merged the fix to the 3.4 branch and released 3.4.3.
I saw in your link you sent me that a core-dump can be made somehow, how can this be done? Because via that core-dump I expect we can pinpoint the reason and confirm the bug for zope.security-3.4.1?
As a first step, I suggest putting 3.4.3 in production and seeing if the segfaults stop. -- Benji York