[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Crash in WIN32 after (supposedly) successful commit

From: Joerg Hessdoerfer <Joerg.Hessdoerfer_at_sea-gmbh.com>
Date: 2003-03-18 09:26:09 CET

Hi,

On Monday 17 March 2003 19:23, Philip Martin wrote:
> Joerg Hessdoerfer <Joerg.Hessdoerfer@sea-gmbh.com> writes:
> > I'll build in the NULL-Ptr check tomorrow (I'm not at the machine
> > anymore) and see what happens.
>
> Try this patch
>
> Index: subversion/libsvn_wc/entries.c
> ===================================================================
> --- subversion/libsvn_wc/entries.c (revision 5358)
> +++ subversion/libsvn_wc/entries.c (working copy)
> @@ -439,7 +439,10 @@
> attributes = svn_xml_make_att_hash (atts, accum->pool);
> err = svn_wc__atts_to_entry (&entry, &modify_flags, attributes,
> accum->pool); if (err)
> - svn_xml_signal_bailout (err, accum->parser);
> + {
> + svn_xml_signal_bailout (err, accum->parser);
> + return;
> + }
>
> /* Find the name and set up the entry under that name. This
> should *NOT* be NULL, since svn_wc__atts_to_entry() should

Yep, that worked, no more crash. I now get the following error instead:

g:\svn\subversion-0.19.1\subversion\libsvn_wc\entries.c:593: (apr_err=125003)
svn: Bogus date
svn: read_entries: xml parser failed (master_progs/WW_MASTER.LLB).
g:\svn\subversion-0.19.1\subversion\libsvn_subr\time.c:183: (apr_err=125003)
svn: Date conversion failed.

which is much more acceptable ;-) (so ignore my previous post about issue
filing...)

Do you submit the patch?

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
Received on Tue Mar 18 09:27:13 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.