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

RE: Exception reporting

From: Bert Huijben <bert_at_qqmail.nl>
Date: Thu, 9 Oct 2014 14:34:45 +0200

> -----Original Message-----
> From: Stefan Sperling [mailto:stsp_at_elego.de]
> Sent: donderdag 9 oktober 2014 12:05
> To: Branko ─îibej
> Cc: Subversion Development
> Subject: Re: Exception reporting
>
> On Thu, Oct 09, 2014 at 06:53:00AM +0200, Branko ─îibej wrote:
> > On 08.10.2014 09:02, Kumar Krishnamoorthy wrote:
> > >
> > > Just reporting it because by subversion client asked me to report it :-)
> > >
> >
> > I'm beginning to wonder if we should ask the TSVN devs to field these
> > crash reports. It's confusing and not very productive for us to get
> > reports of crashes in Tortoise; I'm not saying these crashes "can't"
> > have been caused by Subversion bugs, but it's IMO more efficient to the
> > TSVN devs to do the initial triage and only forward actual bugs here.
> >
> > Not to mention that it turns out that our Windows crash reporting hack
> > is moderately useless, because it doesn't give the report enough context
> > to do anything useful with the report.
> >
> > -- Brane
> >
>
> I agree. I've started to ignore all reports which provide no further
> information than the naked crash report.

It isn't even a crash. It is just the static message from an assertion text. Crashes at least have a dump, but in this case it is a message without any details how anything is called.
(Anything... perhaps even including the commandline which was used to start tsvnproc would add more value)

        Bert
Received on 2014-10-09 14:35:16 CEST

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.