I haven't yet updated my server to te latest version of rivet. So do you advise me to update?
On Wednesday, May 13, 2015, Brice Hamon <[email protected]> wrote: > Hi Massimo, > > I tested your 2.2.2 patched and I don't see the SEGV anymore. I will do > more test over the next days for so far it's looking good. > > Thanks > > Brice. > > On Wed, May 6, 2015 at 10:40 AM, Massimo Manghi <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> Thank you Brice, >> >> the patch plus some extra tests on the page_aborting flag were committed >> and the whole code is now at >> https://svn.apache.org/repos/asf/tcl/rivet/branches/2.2 >> >> -- Massimo >> >> >> On 05/05/2015 01:35 PM, Brice Hamon wrote: >> >>> Hi Massimo, >>> >>> Yes I will. I am up to my neck with my release and did not have one >>> minute to investigate the problem. >>> Once I am free I will work to identify this problem. >>> Thanks >>> Brice. >>> >>> >>> >>> On Tue, May 5, 2015 at 6:51 AM, Massimo Manghi <[email protected] >>> <javascript:_e(%7B%7D,'cvml','[email protected]');> >>> <mailto:[email protected] >>> <javascript:_e(%7B%7D,'cvml','[email protected]');>>> wrote: >>> >>> Hi, I'm still exchanging patches and test results with James, but I >>> will commit the current development status to branches/2.2 and >>> trunk/ because I feel I'm not too far from fixing the long running >>> bug #57501. >>> >>> I found another sore point in the child process exit handler where >>> the Rivet channel could be unregistered several times (one for each >>> virtual host) whereas the Rivet Channel is now unique per child >>> process unless SeparateChannels is on. This condition is now handled >>> consistently. >>> >>> I wonder if this could be the culprit for the segfaults Brice was >>> observing during his tests. Brice, when I commit this stuff in >>> branches/2.2 would you give it a try? Thanks >>> >>> >>> -- Massimo >>> >>> >>> >
