Guten Tag Thorsten Schöning,
am Freitag, 12. April 2019 um 16:25 schrieben Sie:
>> StacktraceSource:
>> #0 object_ref_cleanup (baton=0x7f5f75994f00) at
>> /build/subversion-8E3yhQ/subversion-1.9.3/subversion/libsvn_subr/object_pool.c:148
>>143: */
>>144: static apr_status_t
>>145:
Guten Tag Stefan Sperling,
am Freitag, 12. April 2019 um 11:45 schrieben Sie:
> Install a package with debug symbols, enable core dumps, and get
> a backtrace with gdb from a core dump.
Does the following help? I've attched some more verbose chrashlog
but without the actual dump, as that is some
On Fri, Apr 12, 2019 at 11:42:54AM +0200, Thorsten Schöning wrote:
> Does the error tell anyone of you anything already?
No.
> What should I do
> to get some hints about which repo is affected with which operation?
Install a package with debug symbols, enable core dumps, and get
a backtrace with
Hi all,
today I recognized a segfault in svnserver which seems to have been
documented for UB 16.04 LTS already:
> Apr 12 09:58:55 [...] kernel: [214930.125762] svnserve[556]: segfault at
> 7f5f75994f00 ip 7f5f74ea1065 sp 7ffddc1353f0 error 4 in
> libsvn_subr-1.so.1.0.0[7f5f74e43000+d3
