Created attachment 85685 [details]
New crash information added by DrKonqi

kdesvn (1.6.0) on KDE Platform 4.12.3 using Qt 4.8.5

I attempted to look at the previous entries when viewing the history of the root of my SVN project.

-- Backtrace (Reduced):
#6  0x00007f61a9f68849 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007f61a9f69cd8 in __GI_abort () at abort.c:89
#8  0x00007f61a9f61616 in __assert_fail_base (fmt=0x7f61aa09bf38 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f619a87c028 "svn_uri_is_canonical(child_uri, ((void *)0))", file=file@entry=0x7f619a87bd30 "subversion/libsvn_subr/dirent_uri.c", line=line@entry=1499, function=function@entry=0x7f619a87c3d0 <__PRETTY_FUNCTION__.7467> "uri_skip_ancestor") at assert.c:92
#9  0x00007f61a9f616c2 in __GI___assert_fail (assertion=assertion@entry=0x7f619a87c028 "svn_uri_is_canonical(child_uri, ((void *)0))", file=file@entry=0x7f619a87bd30 "subversion/libsvn_subr/dirent_uri.c", line=line@entry=1499, function=function@entry=0x7f619a87c3d0 <__PRETTY_FUNCTION__.7467> "uri_skip_ancestor") at assert.c:101
#10 0x00007f619a84cd5a in uri_skip_ancestor (parent_uri=0x7f618f794ba0 "http://casvn/svn/octeon", child_uri=0x7f618f794b70 "http://casvn/svn/octeon//sdk-base/trunk/sdk") at subversion/libsvn_subr/dirent_uri.c:1499

Happens to me too. Reproducible all the time. Both with local and remote repositories.

Created attachment 86163 [details]
New crash information added by DrKonqi

kdesvn (1.6.0) on KDE Platform 4.12.4 using Qt 4.8.5

- What I was doing when the application crashed:

Same problem, going back to the previous page causes kdesvn to crash.

-- Backtrace (Reduced):
#6  0x00007fc3a0d2c849 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007fc3a0d2dcd8 in __GI_abort () at abort.c:89
#8  0x00007fc3a0d25616 in __assert_fail_base (fmt=0x7fc3a0e5ff38 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fc391640028 "svn_uri_is_canonical(child_uri, ((void *)0))", file=file@entry=0x7fc39163fd30 "subversion/libsvn_subr/dirent_uri.c", line=line@entry=1499, function=function@entry=0x7fc3916403d0 <__PRETTY_FUNCTION__.7467> "uri_skip_ancestor") at assert.c:92
#9  0x00007fc3a0d256c2 in __GI___assert_fail (assertion=assertion@entry=0x7fc391640028 "svn_uri_is_canonical(child_uri, ((void *)0))", file=file@entry=0x7fc39163fd30 "subversion/libsvn_subr/dirent_uri.c", line=line@entry=1499, function=function@entry=0x7fc3916403d0 <__PRETTY_FUNCTION__.7467> "uri_skip_ancestor") at assert.c:101
#10 0x00007fc391610d5a in uri_skip_ancestor (parent_uri=0x7fc38c080ba0 "http://casvn/svn/octeon", child_uri=0x7fc38c080b70 "http://casvn/svn/octeon//sdk-base/trunk/sdk") at subversion/libsvn_subr/dirent_uri.c:1499

Created attachment 86328 [details]
New crash information added by DrKonqi

kdesvn (1.6.0) on KDE Platform 4.13.0 using Qt 4.8.5

- What I was doing when the application crashed:

Just pushed "Previous entries" button...

-- Backtrace (Reduced):
#11 0x00007fc20ee1ed99 in svn_uri__is_ancestor () from /usr/lib64/libsvn_subr-1.so.0
#12 0x00007fc20e0fbf9d in svn_ra_reparent () from /usr/lib64/libsvn_ra-1.so.0
#13 0x00007fc20e76ee73 in svn_client__ra_session_from_path2 () from /usr/lib64/libsvn_client-1.so.0
#14 0x00007fc20e755fbc in svn_client_log5 () from /usr/lib64/libsvn_client-1.so.0
#15 0x00007fc20f2c268a in svn::Client_impl::log (this=<optimized out>, params=..., log_target=...) at /usr/src/debug/kdesvn-1.6.0/src/svnqt/client_status.cpp:424

Rajko, is it possible to fix this?

Created attachment 86776 [details]
New crash information added by DrKonqi

kdesvn (1.6.0) on KDE Platform 4.13.1 using Qt 4.8.5

- What I was doing when the application crashed:

viewing history and clicked several buttons like "previous"

-- Backtrace (Reduced):
#11 0x00007fcd91d4bd99 in svn_uri__is_ancestor () from /usr/lib64/libsvn_subr-1.so.0
#12 0x00007fcd91028f9d in svn_ra_reparent () from /usr/lib64/libsvn_ra-1.so.0
#13 0x00007fcd9169c203 in svn_client__ra_session_from_path2 () from /usr/lib64/libsvn_client-1.so.0
#14 0x00007fcd9168315c in svn_client_log5 () from /usr/lib64/libsvn_client-1.so.0
#15 0x00007fcd921f068a in svn::Client_impl::log (this=<optimized out>, params=..., log_target=...) at /usr/src/debug/kdesvn-1.6.0/src/svnqt/client_status.cpp:424

Created attachment 87305 [details]
New crash information added by DrKonqi

kdesvn (1.6.40 (rev: 76ac511)) on KDE Platform 4.11.5 using Qt 4.8.5

I tried to view logs too by selecting revisions from 38728 (HEAD) to 36000 and kdesvn crashed when I hit "Get Logs" button.

-- Backtrace (Reduced):
#12 0x4ffbda50 in uri_skip_ancestor () from /lib/libsvn_subr-1.so.0
#13 0x4ffbdaa1 in svn_uri__is_ancestor () from /lib/libsvn_subr-1.so.0
#14 0xb4005e54 in svn_ra_reparent () from /lib/libsvn_ra-1.so.0
#15 0x4ff78a00 in svn_client__ra_session_from_path () from /lib/libsvn_client-1.so.0
#16 0x4ff65e18 in svn_client_log5 () from /lib/libsvn_client-1.so.0

Happens to me too. Always reproductible.

I have the same probem on Debian Testing 64bit.
I created accidential a new bug 337128.

I was able to reproduce the problem with a self compiled version from latest git repository.

I tried to find the code behind that button and was thinking it is SvnLogDlgImp::slotPrevFifty() in src/svnfrontend/svnlogdlgimp.cpp but a breakpoint or a qDebug output get never called.

Does anyone know which code is behind that "get logs" button?

I made a little progress: in kdesvn.cpp the kdesvnpart.so library is loaded. After I pointed to my self compiled version I can debug the problem...

It crashs inside the libsvn library at svnqt/client_status.cpp: 412 at the call to svn_client_log5():

    error = svn_client_log5 (
        params.targets().array (pool),
        params.peg().revision(),
        svn::internal::RevisionRangesToHash(params.revisions()).array(pool),
        params.limit(),
        params.discoverChangedPathes() ? 1 : 0,
        params.strictNodeHistory() ? 1 : 0,
        params.includeMergedRevisions()?1:0,
        params.revisionProperties().array(pool),
        logMapReceiver2,
        &l_baton,
        *m_context, // client ctx
        pool);

Does anyone have an idea whats wrong here?
Is it a libsvn problem ?

*** Bug 337128 has been marked as a duplicate of this bug. ***

It seems like an ABI change in libsvn which wasn't reflected in kdesvn. Is kdesvn maintained, btw?

That might be the case. I have svn 1.8.10 installed.

This is a duplicate of Bug #325074

Fixed with

commit c1adde451dfac202ef63aded5b2a7adfa9e26f9b
Author: Christian Ehrlicher <Ch.Ehrlicher@gmx.de>
Date:   Wed Dec 24 14:44:59 2014 +0100

    REVIEW: 121670
    Patch for Bug 325074 and 330624 - kdesvn crashed when getting logs

(In reply to Christian Ehrlicher from comment #15)
> Fixed with
> 
> commit c1adde451dfac202ef63aded5b2a7adfa9e26f9b
> Author: Christian Ehrlicher <Ch.Ehrlicher@gmx.de>
> Date:   Wed Dec 24 14:44:59 2014 +0100
> 
>     REVIEW: 121670
>     Patch for Bug 325074 and 330624 - kdesvn crashed when getting logs

Ok, thx, but what does it mean?
I use the latest version of Kdesvn (1.6.0), which I can install from my repo (Debian Jessie), and I have same problem with the logs.

What should I do now? Shall I recompile the software from the latest source code? (Where I can download? Is there some installation instruction?) Why it isn't in the main repos?

Any help please!

(In reply to bojti from comment #16)
> (In reply to Christian Ehrlicher from comment #15)
> > Fixed with
> > 
> > commit c1adde451dfac202ef63aded5b2a7adfa9e26f9b
> > Author: Christian Ehrlicher <Ch.Ehrlicher@gmx.de>
> > Date:   Wed Dec 24 14:44:59 2014 +0100
> > 
> >     REVIEW: 121670
> >     Patch for Bug 325074 and 330624 - kdesvn crashed when getting logs
> 
> Ok, thx, but what does it mean?
> I use the latest version of Kdesvn (1.6.0), which I can install from my repo
> (Debian Jessie), and I have same problem with the logs.
> 
> What should I do now? Shall I recompile the software from the latest source
> code? (Where I can download? Is there some installation instruction?) Why it
> isn't in the main repos?
> 
> Any help please!

You do realize that this is not debian bugtracking, right? Distros have package maintainers and you should ask there why debian didn't pick it up. The main reason is that probably there was no official kdesvn release after the bug was fixed, or that the debian package maintainer isn't aware of the fact. What you should do is search debian bugtracking, I'm pretty sure someone reported this bug there years ago, and add a comment mentioning that it's fixed upstream so that they feel motivated to package a new version.

In case you want to build a fixed version locally, your steps will be something like:
1) download the patch fixing the issue (reported on  https://bugs.kde.org/show_bug.cgi?id=325074 ) to e.g. /tmp/fix-log-crash.patch
2) run these in order:
 apt-get source kdesvn
 apt-get build-dep kdesvn
cd kdesvn-1.6.0
 mv /tmp/fix-log-crash.patch debian/patches/
echo fix-log-crash.patch >> debian/patches/series
dpkg-buildpackage -j4 -b
cd ..
dpkg -i kdesvn*.deb

... beware, however, that when you apt-get upgrade/dist-upgrade, apt will override your package with debian one, undoing your changes. There are ways to work around that, google is your friend.

Oh, it solved my problem! Thank you very much!