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 601223 - A normal comment /**/ causes doxy parser to eat all input to end of file
A normal comment /**/ causes doxy parser to eat all input to end of file
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: build
1.6.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-11-09 08:30 UTC by Lucien Murray-Pitts
Modified: 2009-12-30 13:39 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Sample source that will exhibit this behaviour (3.55 KB, application/x-zip-compressed)
2009-11-09 08:30 UTC, Lucien Murray-Pitts 		Details
Same as first attachment, this one compiles under CL too. (3.54 KB, application/x-zip-compressed)
2009-11-09 08:39 UTC, Lucien Murray-Pitts 		Details

Description Lucien Murray-Pitts 2009-11-09 08:30:54 UTC 
Created attachment 147251 [details]
Sample source that will exhibit this behaviour

Acidentally putting a normal comment without spacing causes Doxygen to eat all
input it would seem, without warning?

int asub( 
    int xx,
    /**/
    int zz,
    int aa )
{  // .... 
}

Adding a simple space in there fixes the problem.  I am assuming Doxygen should
see the trailing "/" after "/**" and back-track to a normal comment "/*" "*/" ?
Comment 1 Lucien Murray-Pitts 2009-11-09 08:39:58 UTC 
Created attachment 147253 [details]
Same as first attachment, this one compiles under CL too.
Comment 2 Lucien Murray-Pitts 2009-11-09 08:40:56 UTC 
Comment on attachment 147251 [details]
Sample source that will exhibit this behaviour

This will work in Doxygen, but failes under CL - sorry didnt check it.  Please ref. to Example2 if you need a source that will compile onder Doxy and MSVC CL.
Comment 3 Dimitri van Heesch 2009-11-09 21:09:39 UTC 
Confirmed. Should be fixed in the next subversion update.
Comment 4 Dimitri van Heesch 2009-12-30 13:39:00 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.2. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).