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

segmentation fault in memberdef.cpp (Origin: bugzilla #712795) #5355

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.5-GIT on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-11-21 10:53:51 +0000, Daniel Gröndal wrote:

Created attachment 260412
Suggested patch.

When trying to generate documentation for objective-c I get a segmentation fault in memberdef.cpp.

Running doxygen in gdb it seems the faulting line is memberdef.cpp:812.

if (m_impl->enumFields)
{
MemberListIterator mli(*m_impl->redefinedBy); // <- error here
MemberDef *md;
for (mli.toFirst();(md=mli.current());++mli)
{
result->insertEnumField(md);
}
}

Seems like a typo. Changing the line to:

MemberListIterator mli(*m_impl->enumFields);

seems to fix my segmentation fault and I do get, as far as I can see, correct documentation. I am not sure about the purposed fix since I am not sure on exactly what the code is supposed to do.

I used sha SHA: 5805802 from repo.

On 2013-11-23 13:50:11 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-12-24 19:00:04 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferrably in the form of a self-contained example).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment