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

[PATCH] Doxygen crashes when trying to emit a warning on a function with a % in the method header (C++/CLI) (Origin: bugzilla #643279) #4176

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 critical in component general for ---
Reported in version unspecified on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2011-02-25 11:47:26 +0000, Patrick Grawehr wrote:

Created attachment 181907
Patch file to fix the described issue

When doxygen needs to emit a warning on a function like

CSensorGroup::CSensorGroup(FPMLibrary::CSensorGroup% sg)
{
...
}

(attempting to generate something like:)

D:/Projects/ADS/Software/FCMS/dcl/FPM/FPMLibTestNet/HelperClasses.cpp(305): warning: no uniquely matching class member found for
CSensorGroup::CSensorGroup(FPMLibrary::CSensorGroup% sg)

it crashes.

The reason is that an attempt is made to interpret the method header as format specifier for vfprintf() with no corresponding argument given (note that the declared parameter name starts with an "s"!)

I have attached a patch that fixes the issue (works for me, at least). Oh, and the patch addresses another issue, too: parseCommentAsText() may generate assertions in isspace() if an Utf8 character is encountered. Only "half" the character is passed on to isspace(), because result.at(i) returns just char, not an Utf8 character. That "half" character can be anything, though.

Patrick

On 2011-02-25 19:49:50 +0000, Dimitri van Heesch wrote:

Thanks for your patch. I'll include it (with some adaptations) in the next subversion update.

On 2011-03-28 14:19:35 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.4. 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.

@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