[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: Sander Striker <striker_at_apache.org>
Date: 2003-10-13 14:11:29 CEST

> From: cmpilato@localhost.localdomain
> [mailto:cmpilato@localhost.localdomain]On Behalf Of C. Michael Pilato
> Sent: Saturday, October 11, 2003 3:28 PM

[...]
>> That's true. So maybe it needs to be wrapped in another #if block;
>> SVN_DEBUG_ERROR_LEAK, or something alike?
>
> This is exactly what I was about to do (except, using
> SVN_ERROR_DEBUG). But I don't have time to code or test anything
> right now, so here's the patch (obviously sans-#ifdefs). It's just
> like what Sander sent, except it also removes the aborts before try to
> destroy a child error's pool when that error has been duped into
> another pool.

+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?

Sander

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 13 14:12:18 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.