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 703170 - Segmentation fault parsing a fortran file
Segmentation fault parsing a fortran file
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.4-GIT
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-06-27 08:58 UTC by Thierry Deutsch
Modified: 2013-08-23 15:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Don't recognize type followed by a letter or digit as a type (729 bytes, patch)
2013-06-27 16:51 UTC, albert 		none Details | Review

Description Thierry Deutsch 2013-06-27 08:58:02 UTC 
When parsing this simple fortran program:
program bug
   integer, dimension(2) :: types
   types = 1
end program bug


doxygen has a segmentation fault.
Comment 1 albert 2013-06-27 16:20:30 UTC 
Using a default Doxyfile (doxygen -g).

When running it against 1.8.4 the error messages is:
********************************************************************
Error in file D:/bug_703170/aa.f90 line: 6, state: 17
********************************************************************

the problematic word is "types", when replacing this with e.g. "a_types" everything is working fine.

When running against the git version a crash occurs as well.
Comment 2 albert 2013-06-27 16:51:17 UTC 
Created attachment 247927 [details] [review]
Don't recognize type followed by a letter or digit as a type

Don't recognize type followed by a letter or digit as a type i.e type[^a-z0-9]
Comment 3 Dimitri van Heesch 2013-07-02 14:54:44 UTC 
Thanks, I'll include the patch in the next GIT update.
Comment 4 Dimitri van Heesch 2013-08-23 15:04:40 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.5. 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.