New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
asserts out with template specialization for pointer types with breathe #5496
Comments
Thanks a lot! From your output I think I know what is going on, and is seems I can be triggered as simple as: .. cpp:class:: A
Declaration.
.. cpp:class:: A
Duplicate declaration.
.. cpp:class:: A
Also duplicate, triggers the assert. I'll try to make a fix soon(TM). |
The bug affects me as well and it looks like it was introduced in 1.8.* |
Just ran into this myself. Downgraded and sphinx 1.7 does not have the issue, whereas 1.8 did. |
If a symbol was declared more than 2 times, it would crash. Fixes sphinx-doc#5496.
If a symbol was declared more than 2 times, it would crash. Fixes sphinx-doc#5496.
If a symbol was declared more than 2 times, it would crash. Fixes sphinx-doc#5496.
I think I can only test it with my project locally if I somehow install the PR via pip. But with @t-b 's minimal example I am confident it will work for me as well, otherwise I will report back. |
Great, merged to the 1.8 branch. |
@jakobandersen Could you reopen? With a clean test repo from above the first run passes. But it bugs out on the second run with
third run passes, fourth not and so on. |
ping @jakobandersen there seems to be a regression |
Thanks, I'll take a look at it. |
The assertion problem should be fixed in the 1.8 branch now (really). While it shouldn't crash now, there is still a deeper issue with partial builds and duplicate declarations. Basically, if a declaration is modified/deleted and it has duplicates, then all documents with those duplicates should be rebuild as well. I'm not sure how to trigger this automatically though. |
Problem
Bugs out with the following assertion
C++ declarations:
breathe code.
Procedure to reproduce the problem
Error logs / results
Environment info
The text was updated successfully, but these errors were encountered: