[ 
https://issues.apache.org/jira/browse/SVN-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Zhakov resolved SVN-2122.
------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: unscheduled)
                   1.6.0

Resolving as Fixed. The crash itself was fixed in r851950.

I'm also getting proper output of {{svn st -u}} command using Subversion 1.6.0 
or later:
{noformat}
$ svn st -u wc@246
        *            wc\www\v2\MOVED
        *            wc\www\v2
        *      213   wc\www\docs\domi\debian-kde-debug.html
        *      213   wc\www\docs\domi\debugging-kde-crash.html
        *      213   wc\www\docs\domi\packaging-kde-modules.html
        *            wc\www\docs\faq.html
        *            wc\www\docs\index.html
        *            wc\www\docs\help.html
        *            wc\www\docs\versions.html
        *            wc\www\docs\packages.html
        *            wc\www\docs\people.html
        *            wc\www\docs\descriptions.html
        *            wc\www\docs\install.html
        *      213   wc\www\docs
        *      213   wc\www\IGNORE-ME
        *            wc\www\dummy
        *      213   wc\www
        *      213   wc\scripts\svn-hooks\post-commit
        *      213   wc\scripts\svn-hooks\commit-access-control.cfg
        *      213   wc\scripts\svn-hooks\post-revprop-change
        *      213   wc\scripts\svn-hooks\commit-email.pl
        *            wc\scripts\check-shlibs
        *            wc\scripts\check-shlibs2
        *      213   wc\scripts\IGNORE-ME
        *            wc\scripts\cmake-install-tracer
        *      213   wc\scripts\update-www
        *            wc\scripts\create-buildprep
        *      213   wc\scripts\common
        *            wc\scripts\pull-kde-branch
        *            wc\scripts\filter-buildprep
        *            wc\scripts\autofixtll
        *            wc\scripts\dh_installgen
        *            wc\scripts\sort-install-files
        *            wc\scripts\tag-pkg-kde
        *            wc\scripts\create-icons
        *            wc\scripts\pull-kde4-branch
        *      213   wc\scripts
Status against revision:  20091
{noformat}


> 'svn status -u' can crash with partial -N working copy
> ------------------------------------------------------
>
>                 Key: SVN-2122
>                 URL: https://issues.apache.org/jira/browse/SVN-2122
>             Project: Subversion
>          Issue Type: Bug
>          Components: libsvn_wc
>    Affects Versions: all
>            Reporter: Karl Fogel
>            Assignee: Ben Reser
>             Fix For: 1.6.0
>
>
> Adeodato Simó <[email protected]> posted this report to dev@ today.  The 
> message hasn't shown up in the archives yet, but it's this one:
> {quote}
> From: Adeodato Simó <[email protected]>
> To: [email protected]
> Subject:  crash when doing svn st -u (assertion failed)
> Date: Fri, 12 Nov 2004 00:32:25 +0100
> Message-ID: <[email protected]>
> {quote}
> The recipe is simple, and reproduces for me with svn 1.2 (dev build):
> {noformat}
>  $ svn co -N -r 213 svn://svn.debian.org/pkg-kde .
>  A  README
>  Checked out revision 213.
>  
>  $ svn up -r 213 scripts www
>  [ List of scripts/* files.]
>  Updated to revision 213.
>  [ List of www/* files.]
>  Updated to revision 213.
>    
>  $ svn st -u
>     *      213   www/IGNORE-ME
>     *      213   www
>  svn: subversion/libsvn_wc/status.c:910: tweak_statushash:       \
>     Assertion `repos_text_status == svn_wc_status_added' failed. \
>     Aborted (core dumped)
> {noformat}
> At first, I thought this might be related to SteveKing's status crash bug 
> report, at
>   Original post:
> {quote}
> From: SteveKing <[email protected]>
> Subject:  crash when fetching status
> Message-ID: <[email protected]>
> Date: Tue, 02 Nov 2004 19:44:38 +0100
> http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=82253
> {quote}
>    Whole thread:
>      http://tinyurl.com/4tzqd
> However, looking more closely now, I'm less optimistic that it's the same 
> bug. The assertion that's failing in this new report is one added in r6913, 
> yet it's apparently not being triggered in SteveKing's situation.  
> Investigating now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to