Hi,
Our crash reporting tool already gathered a few crashes in the svn
library. 22 reports are already in with access violations in
svn_relpath_join().
those 22 reports are in two crash groups, but from the stack traces
there are four problems that cause these crashes:
https://www.crash-server.com/Problem.aspx?ClientID=tsvn&ProblemID=1056
and
https://www.crash-server.com/Problem.aspx?ClientID=tsvn&ProblemID=1015
contain all the crash dumps (login info was sent to private@ a while ago)
libsvn_tsvn32!svn_relpath_join+0x10
libsvn_tsvn32!svn_wc__internal_get_origin+0x1b2
libsvn_tsvn32!svn_client_commit5+0x14d3
libsvn_tsvn32!svn_client__harvest_committables+0x26a
libsvn_tsvn32!svn_client_commit5+0x2e4
here the 'status' after svn_wc__db_scan_addition() is
svn_wc__db_status_incomplete which might be an indication why
original_repos_relpath is NULL and then causes the access violation in
svn_relpath_join().
**********
libsvn_tsvn32!svn_relpath_join+0x10
libsvn_tsvn32!svn_wc__internal_get_origin+0x1b2
libsvn_tsvn32!svn_client_diff_summarize_dup+0x56c
libsvn_tsvn32!svn_client_export5+0x1bb
no idea why here original_repos_relpath is NULL though. Maybe you have
more luck analyzing that crash dump.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
