On Tue, Sep 28, 2010 at 07:18:39PM +0100, Philip Martin wrote: > Daniel Näslund <dan...@longitudo.com> writes: > > > On Tue, Sep 28, 2010 at 03:45:33PM +0200, Daniel Shahaf wrote: > >> Daniel Näslund wrote on Mon, Sep 27, 2010 at 22:09:26 +0200: > >> > >> err_abort() is called when an error object hadn't been svn_error_clear()'d. > >> (The error creation installed err_abort() as a pool cleanup callback, > >> and clearing the error unregisters the callback.) > > > > Yes, that was how I understood it. > > If you run the program gdb, it will catch the abort. If you step up > the stack to err_abort and print err[0] then you will see the file and > line where the error was created. (You may well have worked this out > already).
Turned out that it was caused by prop_target->was_deleted (the flag that was set when an error was detected) not beeing initialized to FALSE. Thanks for the suggestion on checking err. Didn't think of that (but I really should have!). Thanks, Daniel
