Moisei Rabinovich wrote:
> On 10/6/06, *D.J. Heap* <email@example.com <mailto:firstname.lastname@example.org>> wrote:
> On 10/3/06, Moisei Rabinovich <email@example.com
> <mailto:firstname.lastname@example.org>> wrote:
> > For svn windows dev: IMHO under any condition the pop up error
> dialog is not
> > acceptable - it freezes the entire process
> > without report an error back to the caller application that is
> the worse
> > behavior one can imagine for any automation system
> > There are some techniques to prevent windows application to
> raise such a
> > dialogs, I would consider to use it for svn application.
> I agree -- can you work up a patch to implement this?
> I can't work on the patch, no time for that, sorry. It requires a deep
> knowledge of the code base that I do not have.
> For the one who (and whether) is going to implement it, I recommend to
> look at
> In particular, SetErrorMode(SEM_FAILCRITICALERRORS); can do the job,
> if the rest of the code matches the conditions defined in the function
> Also _set_se_translator
> could help to get a stack trace on crash and save it in the separate
> file, so it can be investigated later by the developers.
Why do you want to implement your own crashhandler if you can use what
The patch here:
and the modifications I made to the crash reporter used in TSVN
especially due to that request should be more than enough.
The code of the crash reporter dll is here:
Seriously, I'm starting to sense a "not invented here" syndrom...
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Oct 6 21:20:15 2006