Description
Describe the bug
Segmentation fault in addIncludedUsingDirectives
Expected behavior
No segmentation fault
Screenshots
Not appliciable
To Reproduce
Turn on USE_MATHJAX. Any variant appears to trigger the bug. The file it is processing when the fault happens:
Clang assisted parsing was turned off, since I did not manage to compile it due to some problems with llvm packages.
Version
1.9.2
Stack trace
Program received signal SIGSEGV, Segmentation fault.
FileDefImpl::addIncludedUsingDirectives (this=0x555556b1d170, visitedFiles=std::set with 14 elements = {...})
at /dev/shm/doxygen-1.9.2/src/filedef.cpp:1423
1423 ii.fileDef()->addIncludedUsingDirectives(visitedFiles);
(gdb) bt
#0 FileDefImpl::addIncludedUsingDirectives (this=0x555556b1d170, visitedFiles=std::set with 14 elements = {...})
at /dev/shm/doxygen-1.9.2/src/filedef.cpp:1423
#1 0x00005555557a97e8 in FileDefImpl::addIncludedUsingDirectives (this=0x555556b18090,
visitedFiles=std::set with 14 elements = {...}) at /dev/shm/doxygen-1.9.2/src/filedef.cpp:1423
#2 0x00005555556cc41f in findIncludedUsingDirectives () at /dev/shm/doxygen-1.9.2/src/doxygen.cpp:2179
#3 0x0000555555708629 in parseInput () at /dev/shm/doxygen-1.9.2/src/doxygen.cpp:11587
#4 0x00005555556c05b1 in main (argc=1, argv=0x7fffffffdff8) at /dev/shm/doxygen-1.9.2/src/main.cpp:37
(gdb) print m_includeList
$1 = {<std::vector<IncludeInfo, std::allocator<IncludeInfo> >> = std::vector of length 2, capacity 2 = {{
m_fileDef = 0xc, includeName = {m_rep = "type_traits"}, local = false, imported = false}, {m_fileDef = 0x0,
includeName = {m_rep = "string"}, local = false, imported = false}}, <No data fields>}
Additional context
As you can see from my gdb session, I have modified IncludeInfo so I could get some logs:
/** Class representing the data associated with a \#include statement. */
struct IncludeInfo
{
IncludeInfo() {
printf("Ctor %p\n", (void*)this);
}
IncludeInfo(FileDef *fd,const QCString &in,bool loc,bool imp)
: m_fileDef(fd), includeName(in), local(loc), imported(imp) {
printf("Ctor %p in %p\n", (void*)m_fileDef, (const void*)this);
}
FileDef* fileDef() const {
printf("Get filedef %p from %p\n", (void*)m_fileDef, (const void*)this);
fflush(stdout);
return m_fileDef;
}
void fileDef(FileDef& fd) {
m_fileDef = &fd;
}
private:
FileDef *m_fileDef = nullptr;
public:
QCString includeName;
bool local = false;
bool imported = false;
};Then, it is clear that it reads from a IncludeInfo that have never existed. See attached log
log.txt
Get filedef 0xc from 0x55957ca51e60
To me, this looks like some kind of memory corruption, so I tried valgrind, but failed to reproduce the error. When running with valgrind, I see this warning:
/home/torbjorr/Dokument/fruit/lib/event_handler.hpp:25: warning: Detected potential recursive class relation between class fruit::EventHandler and base class fruit::EventHandler< Events... >!
/home/torbjorr/Dokument/fruit/lib/event_handler.hpp:25: warning: Detected potential recursive class relation between class fruit::EventHandler and base class EventHandler< Events... >!
which does not appear without valgrind. As a side note, I think this warning is expected, since Doxygen has no support for recursive inheritance.