On Mon, 8 Nov 2004, Simon Large wrote:
> Branko Cibej wrote:
> > Philip Martin wrote:
> >> Almost all "svn st -u" calls on a non-recursive checkout generate
> >> this
> >> assert if there are updates for things not in the working copy:
> >>
> >> lt-svn: ../svn/subversion/libsvn_wc/status.c:910: tweak_statushash:
> >> Assertion `repos_text_status == svn_wc_status_added' failed.
> >>
> >> What happens on Windows when Subversion asserts?
> >>
> >>
> > My first guess would be that it triggers a "crash" -- i.e., the kind
> > of debug report TSVN seems to hook into.
> >
> kfogel@collab.net wrote:
> > In this case, it seems Philip managed to conjure up the bug just by
> > thinking ("He fixes radios by thinking!"). But if he hadn't done
> > that, the short-term/long-term tradeoff would be a real concern.
>
> Let's not be too hasty here. Philip found the likely cause of an
> assertion failure which may not be well behaved on Windows. But Stefan's
> bug report clearly places the crash on a specific line of code which is
> *not* an assertion. Yes, a good catch, but maybe not the right catch for
I haven't checked our build scripts,, but normally, release builds under
Visual C++ are made with NDEBUG defined, meaning assertions are noops.
Maybe we would crash on the same line if we did that on Unix as well?
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 8 19:55:02 2004