Forgot to "Reply All" (again). Forwarding my reply to the list: On Wed, Jan 22, 2020 at 2:36 PM Daniel Shahaf <[email protected]> wrote: > Nathan Hartman wrote on Wed, 22 Jan 2020 11:00:20 -0500: >> According to the OP's stack trace, the exception was an access >> violation in svn_fs_print_modules(): >> >> Stacktrace: >> #1 0x7fff2af55583 in svn_fs_print_modules() >> #2 0x7fff2af5627d in svn_fs_create2() > > How is this stack state possible? svn_fs_create2() doesn't call > svn_fs_print_modules() directly or indirectly. The latter function > isn't called from _anywhere_ in svnadmin except subcommand_help().
That is really weird. It will take more digging to figure out what happened here. Meanwhile: > Seems to DTRT here: Thanks for testing that. It's comforting to know that invalid inputs don't run us off the road. >> And this patch won't apply because my stupid MUA will change the tabs to >> spaces, but I don't want it to apply because it's incomplete. So this is >> a feature, not a problem. :-) > > Subversion's source code doesn't use tabs I meant the infamous tab between the filename and the revision in the diff header. :-) Cheers, Nathan
