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

Re: Detecting unhandled errors

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2003-10-13 15:41:36 CEST

"Sander Striker" <striker@apache.org> writes:

> +1. I've committed this in rev 7398, with #if ... #endif wrappers.
> 2 tests are failing with this turned on.
> Running all tests in translate-test...FAILURE
> Running all tests in run-fs-tests.py...FAILURE
> I didn't get a core file, nor did gdb help me out when running
> the test in gdb. Running outside gdb however:
> PASS: lt-fs-test 37: ensure no-op for redundant copies
> Aborted
> Clues?

Well, I fully expected things to fail with only the patch I sent. We
still don't have any code cleaning up errors we *do* handle. That is,
the client should be clearing the error chain after it calls
svn_handle_error() (or perhaps svn_handle_error() should remove the
deathly pool cleanup functions).

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 13 15:43:00 2003

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.