On 10/6/06, D.J. Heap <djheap@gmail.com> wrote:
> On 10/3/06, Stefan Küng <tortoisesvn@gmail.com> wrote:
> > Ben Collins-Sussman wrote:
> > > Win32 folks: how do we collect a backtrace in situations like this?
> >
> > must - resist - yelling - told - you - so
> >
> > Issue #1628 (http://subversion.tigris.org/issues/show_bug.cgi?id=1628)
> > is about implementing a crash handler for windows.
> > I've sent in a patch for this, revised version (after some discussions)
> > is still here:
> > http://svn.haxx.se/dev/archive-2005-07/1069.shtml
>
>
> I'd like to look at this further, but I think popping up a box on
> commandline programs is very bad behavior as has been mentioned before
> -- automated processes may not even be running in a visible
> winstation, so the process will be hung forever with no one even able
> to see the dialog.
>
> Can this be tweaked to write out the dump and leave a pointer to it in
> the event log as Brane suggested? Also, what is the license for the
> crashreport dll? Could we just include the code in Windows builds?
The revised patch at the very end of the mailing thread does exactly
that: it prints out an error with the path where the dump file was
written to. And a text to 'please send the dump to
mailaddress@subversion'.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 6 15:24:01 2006