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

Fortran: Stack buffers nested too deeply (Origin: bugzilla #695974) #5124

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status VERIFIED severity normal in component general for ---
Reported in version 1.8.3.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-03-16 18:48:27 +0000, albert wrote:

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.

On 2013-03-16 18:54:37 +0000, albert wrote:

Created attachment 239033
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.

On 2013-03-31 18:05:00 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next subversion update.

On 2013-05-19 12:35:26 +0000, Dimitri van Heesch wrote:

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.

On 2013-05-21 15:49:41 +0000, albert wrote:

Code has been integrated and is working as expected.

@doxygen doxygen closed this Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment