Hi, after having some problems with a memcached configuration in subversions fsfs.conf, which crashed my tracd, I went to the #subversion IRC and also to #trac to find out what the problem was. First, I thought it was some problem with svn 1.8.1 and trac 1.0.1, but then I've been told that if svn_fs_set_warning_func (See: https://subversion.apache.org/docs/api/latest/group__fs__handling.html#gabc881c866ebe2cbd41767374264532e8 ) is not called, Subversion aborts on every warning and therefore crashes either tracd or apache, etc. in such situations. On my machine, Trac always crashed when I was opening the Trac source code browser. So this is very bad, because in fact, Trac should just report the error, log it to stderr, but not crash. And svn developers therefore say that it is mandatory to set this warning function. If the warning function is set, Subversion will not abort and therefore no segfault will happen.. this was hard to debug, until finally somebody on #svn knew what the problem was.
Solution: Implement a warning function which logs the error, and set this function via svn.fs.svn_fs_set_warning_func What do you think? If nobody wants to fix it, I can send in a patch too, but because I am not that familiar with Trac internals, it would be much better if some experienced Trac hackers implement it. Thank you. Best regards, Clemens -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/groups/opt_out.
