After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 643279 - [PATCH] Doxygen crashes when trying to emit a warning on a function with a % in the method header (C++/CLI)
[PATCH] Doxygen crashes when trying to emit a warning on a function with a % ...
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
unspecified
Other Windows
: Normal critical
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-02-25 11:47 UTC by Patrick Grawehr
Modified: 2012-11-18 11:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch file to fix the described issue (2.68 KB, application/octet-stream)
2011-02-25 11:47 UTC, Patrick Grawehr
Details

Description Patrick Grawehr 2011-02-25 11:47:26 UTC
Created attachment 181907 [details]
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
Comment 1 Dimitri van Heesch 2011-02-25 19:49:50 UTC
Thanks for your patch. I'll include it (with some adaptations) in the next subversion update.
Comment 2 Dimitri van Heesch 2011-03-28 14:19:35 UTC
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.