RE: Detecting unhandled errors

> From: cmpilato@localhost.localdomain
> [mailto:cmpilato@localhost.localdomain]On Behalf Of C. Michael Pilato
> Sent: Friday, October 10, 2003 9:53 PM

> Greg Hudson <ghudson@MIT.EDU> writes:

[...]
> > * We should expect this to introduce a period of instability into our
> > client when we first introduce it. Perhaps it should be limited to
> > enable-maintainer-mode builds at least for a while.

It should be enabled only for maintainer mode.

> > * If we ever enable it for non-maintainer-mode builds, perhaps spewing
> > to stderr and exiting would be better than an abort() for those builds.

I'd like to never enable it for non-maintainer-mode.

> > * This will catch errors dropped by applications as well as errors we
> > drop in our own libraries. (At least, if the applications perform an
> > APR shutdown.) That might be considered a little unfriendly; there are
> > many cases where an application doesn't need to care about a small
> > amount of leaked memory, particularly when it only happens a constant
> > number of times.

That's true. So maybe it needs to be wrapped in another #if block;
SVN_DEBUG_ERROR_LEAK, or something alike?
 
> Hmm... good points, all. Must think on these things.

Sander

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 11 10:32:53 2003