Re: Crash in WIN32 after (supposedly) successful commit

Hi again,

On Monday 17 March 2003 19:21, Philip Martin wrote:
> Joerg Hessdoerfer <Joerg.Hessdoerfer@sea-gmbh.com> writes:
> > On Monday 17 March 2003 18:25, Philip Martin wrote:
> > > Joerg Hessdoerfer <Joerg.Hessdoerfer@sea-gmbh.com> writes:
> > > > 'svn status' crashes reproducibly on the WC. When I check out the
> > > > repository to another location, everything seems fine, though.
[...]
>
> <entry
> committed-rev="4"
> name="StartSequencer.vi"
> text-time="1969-12-31T23:00:00.000000Z"
> committed-date="2003-03-17T10:07:55.387935Z"
> checksum="769382c1c08475bff7cfbb9071302ab2"
> last-author="jh"
> kind="file"
> prop-time="2003-03-17T10:00:27.656250Z"/>
>
> The 1969 error causes svn_wc__atts_to_entry to return an error which
> causes handle_start_tag to call svn_xml_signal_bailout. When this
> happens I think handle_start_tag should return immediately and not do
> any further processing.
>
> I don't know why there are dodgy dates in your entries file. What is
> the Windows timestamp on StartSequencer.vi?

Yow! The windows timestamp for this file IS NOT PRESENT! Now talk about an OS!
OK, that explains it (the 2001 dates are OK, this is a very long-running
product...).

After checkout of the repository, everything seems OK, and the file now has a
timestamp. Could be that some CVS-kludge I wrote 4 years ago put an invalid
timestamp on the file (thats about the explanation I have), which triggered
this error.

Should I file an issue for the non-return after bailout? Should invalid dates
be reported somehow, or handled more generously? (Obviously they're
possible!).

Alright then, back to testing...

Greetings,
        Joerg

-- 
Leading SW developer  - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org