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 695974 - Fortran: Stack buffers nested too deeply
Fortran: Stack buffers nested too deeply
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.3.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-03-16 18:48 UTC by albert
Modified: 2013-05-21 15:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
PATCHL: reallocate buffer so no error for nested too deeply can occur (1.13 KB, patch)
2013-03-16 18:54 UTC, albert
none Details | Review

Description albert 2013-03-16 18:48:27 UTC
In the StackOverflow forum the following error message was posted:

Searching for files in directory E:/test
Reading and parsing tag files
Reading E:/test/test1.f90...
Parsing file E:/test/test1.f90...
Exiting...
Stack buffers nested too deeply
*** Doxygen has finished


(see http://stackoverflow.com/questions/15396706/doxygen-with-fortranstack-buffers-nested-too-deeply)

Some investigations lead to:
In the code it is used as a result of a call to the routine pushBuffer. The used stack there has a size of 10, this can be increased. From the code I can see e.g. the situation that this happens when you have quite a few number of statements on one line like:i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; i=1; There is also a condition in the prepass phase but I don't see an example of this that fast.
Comment 1 albert 2013-03-16 18:54:37 UTC
Created attachment 239033 [details] [review]
PATCHL: reallocate buffer so no error for nested too deeply can occur

Replaced the fixed buffer with a reallocated buffer so the problem of the buffer: "Stack buffers nested too deeply" cannot occur anymore.
Comment 2 Dimitri van Heesch 2013-03-31 18:05:00 UTC
Thanks, I'll include the patch in the next subversion update.
Comment 3 Dimitri van Heesch 2013-05-19 12:35:26 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.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.
Comment 4 albert 2013-05-21 15:49:41 UTC
Code has been integrated and is working as expected.