Johan, On Tue, Feb 1, 2011 at 11:16 PM, Johan Corveleyn <jcor...@gmail.com> wrote:
> On Tue, Feb 1, 2011 at 10:10 PM, Johan Corveleyn <jcor...@gmail.com> > wrote: > > it continues until test nr 58, and then gives the popup. > > > > Hm, I'm confused. I guess I'm going to fire up my debugger and set a > > breakpoint or something to see what happens and why ... > > Ok, I'm starting to understand. If I do this with a Debug build, it > crashes without the popup. If I'm running the test with a Release > build, it gives the annoying popup, blocking the rest of the test > suite. > > Is it supposed to be that way? I guess I should just as well be able > to run the full test suite, unattended, with a Release build, no? > The idea was that people who have Visual Studio installed might be more interested in seeing the code resulting in a crash in their debugger than as a textual stacktrace. This choice is hardcoded in subversion/libsvn_subr/win32_crashrpt.c:svn__unhandled_exception_filter (lines 723-724). I'm not against using SVN_DBG_STACKTRACES_TO_STDERR also as a flag to trigger this, or add (yet) another flag. regards, Lieven
