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

Re: Crash report timeout

From: Joseph Galbraith <galb_at_vandyke.com>
Date: 2007-12-27 20:18:10 CET

Simon Large wrote:
> On 27/12/2007, Simon Large <simon.tortoisesvn@googlemail.com> wrote:
>> On 27/12/2007, Stefan Küng <tortoisesvn@gmail.com> wrote:
>>> Simon Large wrote:
>>>> Hi Stefan,
>>>> I notice in the issue tracker that you have put a 3 month time limit
>>>> on crash reports. That set me thinking about different ways of cutting
>>>> down crash reports, or at least filtering them out.
>>>> Is it possible to create some sort of hash based on the stack trace so
>>>> that a particular type of crash can be uniquely identified? I'm saying
>>>> this as one who has never used VC++ so I don't know if this is even
>>>> possible. But if it is, you could add that key to the crashreport
>>>> subject line and get your mail client to filter out all the known
>>>> fixed reports. It could also be used as a query term on our website;
>>>> the crash reporter could provide a link to our site which would tell
>>>> them whether or not that bug is fixed. If it is, there is no need to
>>>> send the crash report at all, and the user can be told where to
>>>> download the new version (if available), or what the workaround is (if
>>>> not).
>>> I think this would be possible, but not really what I want. Sure, a mail
>>> filter could move certain reports to /dev/null, but I could do that even
>>> now for all reports for older versions. What I want is to not even get
>>> those reports anymore.
>>> Besides that, such a hash from the stacktrace wouldn't be really useful:
>>> the stacktraces are just too different from machine to machine even for
>>> the 'same' crash that they won't be of much use.
>> Is there any way of identifying the problem from the crash report, or
>> is the only way to load up VS and find it by eye?
> Of course I mean identifying an already-solved problem, not magically
> identifying the cause of a new problem that no-one has ever seen
> before :-)

You might get something out of WinDBG's analyze -v; I understand
that this is what microsoft uses to sort the crashes being
reported to them.



To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Dec 27 20:15:21 2007

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