Closed dgront closed 5 years ago
Did you build Doxyrest from the latest sources or used the precompiled release v1.1.1? The call stack leads to the location where a bug in the support lib was causing crashes in Doxyrest under certain (usually, invalid or misspelled) command line options. The bug was fixed a while ago, but the binaries for Doxyrest have not been re-released after that.
I have just pushed a tag to re-build the GitHub release with patched support lib (if it passes all tests, Travis CI/Appveyor CI should upload binaries soon).
Meanwhile, one question -- what's the exact command line which leads to a crash?
Also, the above warnings may be safely ignored, the segfault has no connection to those.
OK, so after a few quick tests I learned that "-o" command line flag was mandatory; it was crashing because I didn't use it.
It shouldn't crash even if -o
is omitted. Crash due to wrong/missing paths was fixed quite a while ago. There still was a problem -- doxyrest attempted to generate the output .rst
files in the root directory whenever -o
was omitted. The latest commit fd01477 should take care of that, too
My doxyrest run on Mac OS ends wtih (that is just last 5 lines):
When I try id under lldb, I see that:
I understand the problem comes from the missing nodes (e.g. d0/d29/classstd_1_1wstringstream), but in fact I'm absolutely interested in them. All the missing nodes concern standard C++ libary which I'm not willing to document. Can doxyrest just go over this errors?