Hi,
On Wed, Apr 28, 2021 at 5:39 PM Rick van der Zwet
wrote:
> > Ack, but the backtrace does go through Subversion's swig-py bindings and
> > libsvn_fs_fs, so we might be involved nevertheless.
>
> ...
>
> error which seems to be related to the Trac code, I filled it over
> there:
On 2021-04-23 15:31, Daniel Shahaf wrote:
> Rick van der Zwet wrote on Fri, Apr 23, 2021 at 02:57:02 +0200:
>> FYI: I did some futher investigation on the specific problem within Trac
>> I was trying to fix and I am getting more hints by experimenting with
>> flags and combinations. If I compile
Rick van der Zwet wrote on Fri, Apr 23, 2021 at 02:57:02 +0200:
> I really liked the suggestions provided, they gave me the clearity I
> needed with regards the lifetime debug flagging on 'svn help' output,
> thanks!
You're welcome.
> FYI: I did some futher investigation on the specific problem
On 2021-04-21 21:35, Daniel Shahaf wrote:
> Rick van der Zwet wrote on Wed, Apr 21, 2021 at 16:10:57 +0200:
>> Hi,
>>
>> I debugging crashes within the Trac (https://trac.edgewall.org/) when using
>> the svn backend. The issue seems to be related to Apache Portable Runtime
>> (APR) pool memory
Rick van der Zwet wrote on Wed, Apr 21, 2021 at 16:10:57 +0200:
> Hi,
>
> I debugging crashes within the Trac (https://trac.edgewall.org/) when using
> the svn backend. The issue seems to be related to Apache Portable Runtime
> (APR) pool memory management at Trac together with subversion SWIG
Hi,
I debugging crashes within the Trac (https://trac.edgewall.org/) when
using the svn backend. The issue seems to be related to Apache Portable
Runtime (APR) pool memory management at Trac together with subversion
SWIG python bindings and libsvn.
I am trying to run subverion with APR
