doxygen-users — List for users of doxygen

Re: [Doxygen-users] need custom footer w/treeview

[Monique S. <mon...@ea...>]

SOLVED!
The footer *was* actually being included, but needed to be edited. I hadn’t noticed in the model default header that there were two separate sections, one for when the treeview is used, and a 2nd one for when it’s not used. And I’d customized only the not-treeview section. So as soon as I customized the treeview section, too, it appeared :-).
So false alarm, and thanks for Damon for saying that it worked for you. It lead me to proper debugging.
-Monique

Re: [Doxygen-users] need custom footer w/treeview

[Monique S. <mon...@ea...>]

> You may need to set DISABLE_INDEX = YES to remove the redundant row of tabs for the treeview output to work correctly.
Hmm... I already have DISABLE_INDEX = YES, and (correctly) I am not getting redundant tabs. The problem is that I am not getting my custom footer, which I want.
That is, with DISABLE_INDEX and GENERATE_TREEVIEW both set to NO, I get the tabs-on-top and my custom footer.
But with DISABLE_INDEX and GENERATE_TREEVIEW both set to YES, I get the “frames” view but NO custom footer.
And what I want is the “frames” view AND the custom footer.
So something else must be going wrong.
-Monique

[Doxygen-users] need custom footer w/treeview

[Monique S. <mon...@ea...>]

Hello, doxygen-users,

I’m a newbie Doxygen user, using doxygen 1.8.5 on a Linux system. Input is C++, output is HTML.

I’d like to include a copyright/legal notice in the footer. I had no trouble creating a custom footer HTML file and getting it into my output. And I further customized its appearance by creating a custom CSS and referencing it in the HTML_EXTRA_STYLESHEET  option.

But then in my Doxyfile config file, I set the GENERATE_TREEVIEW to YES, and the custom footer disappeared! When I reset that option to NO, and return to the default tabs-at-the-top format, the custom footer returns.

My CSS and HTML knowledge isn’t very deep, so perhaps the issue is that in “frame-like” pages you can’t include a footer? But the default “Generated by doxygen 1.8.5” info *IS* appearing below the “frameset”. So something obviously can be place at the bottom of the page. And so I’d like it to be my copyright/legal notice.

Any suggestions?

Thanks so much,
-Monique

[Doxygen-users] search.php and Request.pm interaction causing searches to fail

[Suzanne B. <dpr...@ya...>]

    
Hello,

I am new to working with the doxygen files and with php in general so I am hoping that someone can help me.  

We are using Doygen version 1.8.3.1 and php version 5.2.17.  Doxygen is built with SEARCHENGINE = YES, SERVER_BASED_SEARCH = NO, and EXTERNAL_SEARCH = NO in Doxyfile.

My problem is that when search.php is being called, the call ends up in Request.pm which then opens the following command 
     /usr/local/php/bin/php  /htdocs/CS/doxygen/search.php 'query=$params->{query}'  2>&1
This does call search.php, however my value for query is now in $argv rather than $_GET where search-functions.php file expects it to be.  If I modify search.php to put the value from $argv into $_GET I do get the correct results.  
I am not sure why the call to search.php is ending up in Request.pm.  I do not know see any calls for Request.pm in the doxygen code.  I do not know if Request.pm is always used if Apache is set up a certain way, or if php can be set to use Request.pm.  We build Doxygen for each software release; which means that we build a new Doxygen directory at least twice a year.  I am not sure that I should be changing search.php at all, but I particularly don't want to have to implement the same change each time we build for a release.  

Is it safe to change search.php?  Is there a core source file that I can change it so that it is automatically picked up for each new build?  Or, alternatively, does anyone know anything about Request.pm and how that would be intercepting the search.php call on apache?

Any information that you can provide would be greatly appreciated.

Thank you,

Sue

Re: [Doxygen-users] Can doxygen do this (including not only examples, but also their output )?

[Stephan P. <ste...@gm...>]

Hi Peter,

> We[1] use a combination of doxygen (for API) and Sphinx[2] for more
> expository docs, such as tutorial and manual. 

thanks for pointing out Sphinx, I had not heard of it until now.

> In particular, it's
> straightforward Sphinx to integrate portions of an example program
> along with the output.  Sphinx uses make to generate the
> documentation, so it's also straightforward to build and run the
> example code as part of building the documentation.

Sounds good. When you make changes to example programs which changes
their output, then rerun your make-based documentation creation process,
is the changed output automatically reflected in the docs?

The way I do it in my old Yodl-based documentation is that an example
program has for instance the line
printf("###include###\n");
at the position where a chunk of output should be displayed. A Perl
script would then take the source code and the program's output and
replace the printf("###include###\n") lines with the chunks of output.
Is your Sphinx-based system similar? I'm just trying get a head start on
understanding which features of Sphinx I need to look at to judge how
this could be done.

Thanks and all the best,

Stephan

Re: [Doxygen-users] Can doxygen do this (including not only examples, but also their output )?

[Stephan P. <ste...@gm...>]

Hi Scott,

thanks a lot for your quick reply.

> Have you looked at other options such as latex or 
> docbook(http://www.docbook.org/)?
> If the code isn't the issue, maybe another documentation language would 
> be useful?

Actually, I had decided to take a closer look at doxygen and Docbook.
Since Docbook and the necessary tool chain looked a bit daunting, I
decided to give doxygen a try first :-). But since I would not really be
using it for what it was primarily intended (at least for this project),
it could be doxygen is not the optimal tool...

All the best,

Stephan

Re: [Doxygen-users] Can doxygen do this (including not only examples, but also their output )?

[Barnes, P. D. <bar...@ll...>]

Hello Stephan,

We[1] use a combination of doxygen (for API) and Sphinx[2] for more expository docs, such as tutorial and manual.  In particular, it's straightforward Sphinx to integrate portions of an example program along with the output.  Sphinx uses make to generate the documentation, so it's also straightforward to build and run the example code as part of building the documentation.

Peter

[1]  https://www.nsnam.org/docs/release/3.19/tutorial/html/index.html
https://www.nsnam.org/docs/release/3.19/manual/html/index.html

[2]  http://sphinx-doc.org

On May 19, 2014, at 7:17 AM, Stephan Petersen <ste...@gm...> wrote:
> I'm new to doxygen and I'm currently trying to figure out whether it's
> the right tool for the job.
> - short (but complete) example programs that illustrate the use of all
> the functions the library provides, currently in C and Fortran, but
> potentially later also in Pascal/Python/Java.
> 
> The latter is where I'm currently not 100% sure whether and how it can
> be done with doxygen, since what I would like to do looks like this:
> 
> http://gtt.mch.rwth-aachen.de/gtt-web/Software/ChemApp/CAL-DOC/cal62.html#l100
> 
> Stephan

_______________________________________________________________________
Dr. Peter D. Barnes, Jr.                Physics Division
Lawrence Livermore National Laboratory  Physical and Life Sciences
7000 East Avenue, L-50                  email:  pdb...@ll...
P. O. Box 808                           Voice:  (925) 422-3384
Livermore, California 94550             Fax:    (925) 423-3371

Re: [Doxygen-users] Can doxygen do this (including not only examples, but also their output )?

[Scott F. <sco...@gm...>]

On 19/05/14 08:17 AM, Stephan Petersen wrote:
> Free flowing text with tables, graphics, lists, links, etc. (no
> problem for doxygen, although I did have to improvise a little already
> in my tests:-)  )
Have you looked at other options such as latex or 
docbook(http://www.docbook.org/)?
If the code isn't the issue, maybe another documentation language would 
be useful?
Just a suggestion.

[Doxygen-users] Can doxygen do this (including not only examples, but also their output )?

[Stephan P. <ste...@gm...>]

Hi everyone,

I'm new to doxygen and I'm currently trying to figure out whether it's
the right tool for the job. I believe it is, since I've done a few
tests, but before I run into a time-consuming dead end I just wanted to
ask if anybody can tell me weather certain things are indeed possible.

The "job" is the manual for a code library (from the area of
thermochemistry, if anyone cares to know :-) ), and it does NOT involve
documenting the source code of the library itself. Actually, it doesn't
even matter in which language the library is coded (it's Fortran), since
doxygen doesn't need to touch this code.

The key components of the documentation are:

- Free flowing text with tables, graphics, lists, links, etc. (no
problem for doxygen, although I did have to improvise a little already
in my tests :-) )

- short (but complete) example programs that illustrate the use of all
the functions the library provides, currently in C and Fortran, but
potentially later also in Pascal/Python/Java.

The latter is where I'm currently not 100% sure whether and how it can
be done with doxygen, since what I would like to do looks like this:

http://gtt.mch.rwth-aachen.de/gtt-web/Software/ChemApp/CAL-DOC/cal62.html#l100

(This is btw. an older version of the documentation which I started in
the late 90s, I used "Yodl" for this, plus a number of custom Perl
scripts run via Makefiles for pre- and postprocessing. But I'd like to
move away from Yodl to a more "active" tool with a larger user base...)

You can see that I splice chunks of output of the very sample programs
into the documented code. In fact, the output is generated from the
current version of the library automatically right before the
documentation is made.

Some example programs write the calculated results to output files that
I process with gnuplot into images and again insert back into the
documented code:

http://gtt.mch.rwth-aachen.de/gtt-web/Software/ChemApp/CAL-DOC/cal81.html#l122

Another important detail is that all calls to the library's few dozen
subroutines are all cross-linked. This is normally not a problem for
doxygen, but in my case I am *not* scanning the source code of the
library, and using \fn instead does not seem to the trick yet.

I did have a look at \dontinclude and related commands, but out of the
box none of them quite seem to fit my bill...

Does anybody out there use doxygen in such a way? Is that possible? One
way or the other I'm sure it is, but I'd like to get a feeling for how
easy or tricky it is, in order to judge how big a project the conversion
from Yodl to doxygen would be.

Thanks in advance for any pointers,

Stephan

[Doxygen-users] No documentation generated for method-less struct

[John Y. <jo...@ya...>]

It seems that if a struct (but not a class) has no constructor(s), nor
destructor(s), nor methods then no documentation gets generated.  Here is
my doxygen_bug.hpp:

----------
struct Bar {
  int x;
};

struct Foo {
  void m();
  int x;
};

struct Waz {
  int x;
  int y;
};
----------

Documentation gets generated for Foo but not for Bar nor Waz.

I have doxygen images built from source snapshots on 4/7, 4/18, 4/28 and
5/13.  All exhibit the same behavior.

In case it is important here are my non-standard settings:

----------
ALPHABETICAL_INDEX     = YES
ALWAYS_DETAILED_SEC    = YES
BUILTIN_STL_SUPPORT    = YES
CALLER_GRAPH           = YES
CALL_GRAPH             = YES
# CLANG_ASSISTED_PARSING = YES
COLS_IN_ALPHA_INDEX    = 4
COMPACT_LATEX          = YES
DOT_IMAGE_FORMAT       = svg
DOT_MULTI_TARGETS      = YES
ENUM_VALUES_PER_LINE   = 0
EXTENSION_MAPPING      = cgr=C++,gt=C++
EXTRACT_ALL            = YES
EXTRACT_ANON_NSPACES   = YES
EXTRACT_PACKAGE        = YES
EXTRACT_PRIVATE        = YES
EXTRACT_STATIC         = YES
EXCLUDE                = test tests
FILTER_SOURCE_FILES    = YES
FORCE_LOCAL_INCLUDES   = YES
FULL_PATH_NAMES        = NO
GENERATE_LATEX         = YES
GENERATE_TREEVIEW      = YES
HAVE_DOT               = YES
HIDE_UNDOC_RELATIONS   = NO
HTML_DYNAMIC_SECTIONS  = YES
INLINE_INFO            = NO
INLINE_SIMPLE_STRUCTS  = YES
INTERACTIVE_SVG        = YES
JAVADOC_AUTOBRIEF      = YES
LATEX_BATCHMODE        = YES
LATEX_HIDE_INDICES     = YES
LOOKUP_CACHE_SIZE      = 2
MACRO_EXPANSION        = YES
MAN_LINKS              = YES
MAX_DOT_GRAPH_DEPTH    = 1000
PAPER_TYPE             = letter
PDF_HYPERLINKS         = YES
QUIET                  = YES
RECURSIVE              = YES
REFERENCED_BY_RELATION = YES
REFERENCES_LINK_SOURCE = NO
REFERENCES_RELATION    = YES
SEPARATE_MEMBER_PAGES  = YES
SKIP_FUNCTION_MACROS   = NO
SORT_MEMBERS_CTORS_1ST = YES
SOURCE_BROWSER         = YES
STRIP_CODE_COMMENTS    = NO
SUBGROUPING            = NO
TAB_SIZE               = 8
TEMPLATE_RELATIONS     = YES
TOC_EXPAND             = YES
USE_HTAGS              = YES
USE_PDFLATEX           = YES
----------

/john

Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4

[Fabian N. <fab...@sc...>]

Yes it does.

So from what I'm seeing at the moment, the old versions seem to ignore the EXTENSION_MAPPING = f90=FortranFree ?! (thus mapping f90 to Fortran)
That would be good, since per default our machines run doxygen 1.6.1 and it would be nice if we could all use the same config file...

Fabian

----- Original Message -----
> From: "Albert" <alb...@gm...>
> To: "Fabian Nick" <fab...@sc...>
> Cc: dox...@li...
> Sent: Wednesday, 14 May, 2014 3:01:40 PM
> Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4
> 
> 
> 
> 
> Hi Fabian,
> 
> No problem, so in the new version it works OK.
> 
> Albert
> 
> 
> 
> 
> On Wed, May 14, 2014 at 3:00 PM, Fabian Nick <
> fab...@sc... > wrote:
> 
> 
> Sorry - right version, but wrong syntax...
> 
> 
> ----- Original Message -----
> > From: "Albert" < alb...@gm... >
> > To: "Fabian Nick" < fab...@sc... >
> > Cc: dox...@li...
> 
> 
> > Sent: Wednesday, 14 May, 2014 2:57:10 PM
> > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state
> > 4
> > 
> > 
> > 
> > 
> > Hi Fabian,
> > 
> > In which version of doxygen did you try the EXTENSION_MAPPING as it
> > is new to version 1.8.7?
> > 
> > Albert
> > 
> > 
> > 
> > 
> > On Wed, May 14, 2014 at 2:54 PM, Fabian Nick <
> > fab...@sc... > wrote:
> > 
> > 
> > Hi Albert,
> > 
> > thanks for your efforts.
> > 
> > Since the error only occured in one file, I think we can live with
> > this quick fix for the time being.
> > We'll have to see how our usage of Doxygen develops anyway. (Our
> > code
> > has grown over quite some years already so it won't be easy do
> > document everything and have a nice and clean documentation)
> > 
> > Regarding the EXTENSION_MAPPING parameter: I tried setting it to
> > FortranFree but the error still occured in the "non-fixed" version
> > of the source file.
> > 
> > Best regards,
> > 
> > Fabian
> > 
> > ----- Original Message -----
> > > From: "Albert" < alb...@gm... >
> > > To: "Fabian Nick" < fab...@sc... >
> > > Cc: dox...@li...
> > 
> > 
> > > Sent: Tuesday, 13 May, 2014 7:56:38 PM
> > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468,
> > > state
> > > 4
> > > 
> > > 
> > > Posting on forum as well.
> > > 
> > > 
> > > 
> > > 
> > > 
> > > On Tue, May 13, 2014 at 7:46 PM, Albert < alb...@gm...
> > > >
> > > wrote:
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Hi Fabian,
> > > 
> > > I had a quick look.
> > > 
> > > In version 1.8.7 placing as first line"
> > > !
> > > 
> > > i.e. a space followed by an exclamation mark solves the problem.
> > > 
> > > In version 1.6.1 the file is still preprocessed but the error is
> > > gone
> > > and the file looks OK (but maybe in more complex situations
> > > problems
> > > do occur).
> > > 
> > > 
> > > Determination of free or fixed formatted code is not really
> > > possible
> > > there are always exceptions possible. In compilers this is often
> > > solved by means of the extension and a switch. In doxygen 1.8.7
> > > the
> > > possibility exists to specify the type (free or fixed formatted)
> > > Fortran code by means of EXTENSION_MAPPING in the Doxyfile:
> > > # Doxygen selects the parser to use depending on the extension of
> > > the
> > > files it
> > > # parses. With this tag you can assign which parser to use for a
> > > given
> > > # extension. Doxygen has a built-in mapping, but you can override
> > > or
> > > extend it
> > > # using this tag. The format is ext=language, where ext is a file
> > > extension, and
> > > # language is one of the parsers supported by doxygen: IDL, Java,
> > > Javascript,
> > > # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format
> > > Fortran:
> > > # FortranFixed, free formatted Fortran: FortranFree, unknown
> > > formatted Fortran:
> > > # Fortran. In the later case the parser tries to guess whether
> > > the
> > > code is fixed
> > > # or free formatted code, this is the default for Fortran type
> > > files), VHDL. For
> > > # instance to make doxygen treat .inc files as Fortran files
> > > (default
> > > is PHP),
> > > # and .f files as C (default is Fortran), use: inc=Fortran f=C.
> > > #
> > > # Note For files without extension you can use no_extension as a
> > > placeholder.
> > > #
> > > # Note that for custom extensions you also need to set
> > > FILE_PATTERNS
> > > otherwise
> > > # the files are not read by doxygen.
> > > 
> > > EXTENSION_MAPPING =
> > > 
> > > 
> > > 
> > > 
> > > Albert
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > On Tue, May 13, 2014 at 2:15 PM, Albert < alb...@gm...
> > > >
> > > wrote:
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Hi Fabian,
> > > 
> > > Very nice small example. I'll have a look in the evening.
> > > 
> > > Albert
> > > 
> > > (got message through both channels)
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > On Tue, May 13, 2014 at 1:42 PM, Fabian Nick <
> > > fab...@sc... > wrote:
> > > 
> > > 
> > > Hi Albert,
> > > 
> > > unfortunately I cannot send you the source file. However I was
> > > able
> > > to boil it down to the one attached. For convenience, I also
> > > attached the config file I used (it's just the one generated by
> > > doxygen -g though...)
> > > 
> > > Notice the leading blanks.
> > > The version attached does NOT work. However, if there are equally
> > > many leading blanks before "subroutine testsub" and "end
> > > subroutine"
> > > it works!
> > > Also, removing the module declarations helps as well.
> > > 
> > > If you need more information, just let me know!
> > > 
> > > Thanks,
> > > 
> > > Fabian
> > > 
> > > ----- Original Message -----
> > > > From: "Albert" < alb...@gm... >
> > > > To: "Fabian Nick" < fab...@sc... >
> > > > Cc: dox...@li...
> > > 
> > > 
> > > > Sent: Tuesday, 13 May, 2014 1:12:57 PM
> > > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468,
> > > > state
> > > > 4
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Hi Fabian,
> > > > 
> > > > 
> > > > It is always hard to find these kind of errors. What I do is
> > > > that
> > > > I
> > > > reduce the file and see what happens (good old trial and error
> > > > removing half of the file etc.).
> > > > 
> > > > Is it possible for you to post the file? (I could have a look
> > > > in
> > > > the
> > > > evening.
> > > > 
> > > > Albert
> > > > 
> > > > 
> > > > 
> > > > 
> > > > On Tue, May 13, 2014 at 1:07 PM, Fabian Nick <
> > > > fab...@sc... > wrote:
> > > > 
> > > > 
> > > > Hi Albert,
> > > > 
> > > > no the Prepassing line is not present. Just "preprocessing..."
> > > > and
> > > > "parsing..."
> > > > I tried the extra line starting with "!" anyway, but it didn't
> > > > help.
> > > > 
> > > > Using 1.8.7 didn't help either, however the error is now
> > > > reported
> > > > in
> > > > line 3467 (as opposed to 3468 before).
> > > > 
> > > > And yes, the file does compile properly.
> > > > Are there any constructs (like strings containing '!' in the
> > > > source)
> > > > I could look out for?
> > > > 
> > > > Regards,
> > > > Fabian
> > > > 
> > > > 
> > > > 
> > > > ----- Original Message -----
> > > > > From: "Albert" < alb...@gm... >
> > > > > To: "Fabian Nick" < fab...@sc... >
> > > > > Cc: dox...@li...
> > > > > Sent: Tuesday, 13 May, 2014 12:55:10 PM
> > > > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468,
> > > > > state
> > > > > 4
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > Hi Fabian,
> > > > > 
> > > > > The line number is the number where it saw a problem and in
> > > > > this
> > > > > case
> > > > > this is when the file has been completely parsed.
> > > > > The state 4 means an error with SubprogBody, so something not
> > > > > ended
> > > > > properly (I assume the file compiles properly).
> > > > > 
> > > > > You are using version 1.6.1 and the current version is 1.8.7
> > > > > so
> > > > > an
> > > > > upgrade would certainly help.
> > > > > During the run does it say something about prepassing XX.f90
> > > > > ?
> > > > > so like:
> > > > > Reading .../XX.f90
> > > > > Prepassing fixed form of .../XX.f90
> > > > > Parsing file XX.f90
> > > > > 
> > > > > The line
> > > > > Prepassing fixed form of .../XX.f90
> > > > > should not be present, if present try to place a ! as fist
> > > > > line
> > > > > in
> > > > > the XX.f90 file.
> > > > > 
> > > > > 
> > > > > Anyhow upgrading to 1.8.7 is a very good idea.
> > > > > 
> > > > > 
> > > > > Albert
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > On Tue, May 13, 2014 at 11:46 AM, Fabian Nick <
> > > > > fab...@sc... > wrote:
> > > > > 
> > > > > 
> > > > > Hi everyone,
> > > > > 
> > > > > when trying to run doxygen on a large (Fortran-)project, I
> > > > > get
> > > > > the
> > > > > "Error in file XX.f90 line:3468, state 4" error. The
> > > > > interesting
> > > > > thing is that the file only has 3466 lines...
> > > > > The file is in fixed format. Somewhere on the web it was said
> > > > > that
> > > > > enabling the C-preprocessor might help but it doesn't in my
> > > > > case.
> > > > > I
> > > > > also read that there was a bug which was fixed in version
> > > > > 1.5.6
> > > > > (I
> > > > > think), however I'm using version 1.6.1.
> > > > > 
> > > > > Any advice on what I could try?
> > > > > 
> > > > > Regards,
> > > > > Fabian
> > > > > 
> > > > > ------------------------------------------------------------------------------
> > > > > "Accelerate Dev Cycles with Automated Cross-Browser Testing -
> > > > > For
> > > > > FREE
> > > > > Instantly run your Selenium tests across 300+ browser/OS
> > > > > combos.
> > > > > Get unparalleled scalability from the best Selenium testing
> > > > > platform
> > > > > available
> > > > > Simple to use. Nothing to install. Get started now for free."
> > > > > http://p.sf.net/sfu/SauceLabs
> > > > > _______________________________________________
> > > > > Doxygen-users mailing list
> > > > > Dox...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> > > > > 
> > > > > 
> > > > 
> > > > 
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> 
> 

Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4

[Albert <alb...@gm...>]

Hi Fabian,

No problem, so in the new version it works OK.

Albert


On Wed, May 14, 2014 at 3:00 PM, Fabian Nick <fab...@sc...
> wrote:

> Sorry - right version, but wrong syntax...
>
> ----- Original Message -----
> > From: "Albert" <alb...@gm...>
> > To: "Fabian Nick" <fab...@sc...>
> > Cc: dox...@li...
> > Sent: Wednesday, 14 May, 2014 2:57:10 PM
> > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4
> >
> >
> >
> >
> > Hi Fabian,
> >
> > In which version of doxygen did you try the EXTENSION_MAPPING as it
> > is new to version 1.8.7?
> >
> > Albert
> >
> >
> >
> >
> > On Wed, May 14, 2014 at 2:54 PM, Fabian Nick <
> > fab...@sc... > wrote:
> >
> >
> > Hi Albert,
> >
> > thanks for your efforts.
> >
> > Since the error only occured in one file, I think we can live with
> > this quick fix for the time being.
> > We'll have to see how our usage of Doxygen develops anyway. (Our code
> > has grown over quite some years already so it won't be easy do
> > document everything and have a nice and clean documentation)
> >
> > Regarding the EXTENSION_MAPPING parameter: I tried setting it to
> > FortranFree but the error still occured in the "non-fixed" version
> > of the source file.
> >
> > Best regards,
> >
> > Fabian
> >
> > ----- Original Message -----
> > > From: "Albert" < alb...@gm... >
> > > To: "Fabian Nick" < fab...@sc... >
> > > Cc: dox...@li...
> >
> >
> > > Sent: Tuesday, 13 May, 2014 7:56:38 PM
> > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state
> > > 4
> > >
> > >
> > > Posting on forum as well.
> > >
> > >
> > >
> > >
> > >
> > > On Tue, May 13, 2014 at 7:46 PM, Albert < alb...@gm... >
> > > wrote:
> > >
> > >
> > >
> > >
> > >
> > > Hi Fabian,
> > >
> > > I had a quick look.
> > >
> > > In version 1.8.7 placing as first line"
> > > !
> > >
> > > i.e. a space followed by an exclamation mark solves the problem.
> > >
> > > In version 1.6.1 the file is still preprocessed but the error is
> > > gone
> > > and the file looks OK (but maybe in more complex situations
> > > problems
> > > do occur).
> > >
> > >
> > > Determination of free or fixed formatted code is not really
> > > possible
> > > there are always exceptions possible. In compilers this is often
> > > solved by means of the extension and a switch. In doxygen 1.8.7 the
> > > possibility exists to specify the type (free or fixed formatted)
> > > Fortran code by means of EXTENSION_MAPPING in the Doxyfile:
> > > # Doxygen selects the parser to use depending on the extension of
> > > the
> > > files it
> > > # parses. With this tag you can assign which parser to use for a
> > > given
> > > # extension. Doxygen has a built-in mapping, but you can override
> > > or
> > > extend it
> > > # using this tag. The format is ext=language, where ext is a file
> > > extension, and
> > > # language is one of the parsers supported by doxygen: IDL, Java,
> > > Javascript,
> > > # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format
> > > Fortran:
> > > # FortranFixed, free formatted Fortran: FortranFree, unknown
> > > formatted Fortran:
> > > # Fortran. In the later case the parser tries to guess whether the
> > > code is fixed
> > > # or free formatted code, this is the default for Fortran type
> > > files), VHDL. For
> > > # instance to make doxygen treat .inc files as Fortran files
> > > (default
> > > is PHP),
> > > # and .f files as C (default is Fortran), use: inc=Fortran f=C.
> > > #
> > > # Note For files without extension you can use no_extension as a
> > > placeholder.
> > > #
> > > # Note that for custom extensions you also need to set
> > > FILE_PATTERNS
> > > otherwise
> > > # the files are not read by doxygen.
> > >
> > > EXTENSION_MAPPING =
> > >
> > >
> > >
> > >
> > > Albert
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Tue, May 13, 2014 at 2:15 PM, Albert < alb...@gm... >
> > > wrote:
> > >
> > >
> > >
> > >
> > >
> > > Hi Fabian,
> > >
> > > Very nice small example. I'll have a look in the evening.
> > >
> > > Albert
> > >
> > > (got message through both channels)
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Tue, May 13, 2014 at 1:42 PM, Fabian Nick <
> > > fab...@sc... > wrote:
> > >
> > >
> > > Hi Albert,
> > >
> > > unfortunately I cannot send you the source file. However I was able
> > > to boil it down to the one attached. For convenience, I also
> > > attached the config file I used (it's just the one generated by
> > > doxygen -g though...)
> > >
> > > Notice the leading blanks.
> > > The version attached does NOT work. However, if there are equally
> > > many leading blanks before "subroutine testsub" and "end
> > > subroutine"
> > > it works!
> > > Also, removing the module declarations helps as well.
> > >
> > > If you need more information, just let me know!
> > >
> > > Thanks,
> > >
> > > Fabian
> > >
> > > ----- Original Message -----
> > > > From: "Albert" < alb...@gm... >
> > > > To: "Fabian Nick" < fab...@sc... >
> > > > Cc: dox...@li...
> > >
> > >
> > > > Sent: Tuesday, 13 May, 2014 1:12:57 PM
> > > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468,
> > > > state
> > > > 4
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hi Fabian,
> > > >
> > > >
> > > > It is always hard to find these kind of errors. What I do is that
> > > > I
> > > > reduce the file and see what happens (good old trial and error
> > > > removing half of the file etc.).
> > > >
> > > > Is it possible for you to post the file? (I could have a look in
> > > > the
> > > > evening.
> > > >
> > > > Albert
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, May 13, 2014 at 1:07 PM, Fabian Nick <
> > > > fab...@sc... > wrote:
> > > >
> > > >
> > > > Hi Albert,
> > > >
> > > > no the Prepassing line is not present. Just "preprocessing..."
> > > > and
> > > > "parsing..."
> > > > I tried the extra line starting with "!" anyway, but it didn't
> > > > help.
> > > >
> > > > Using 1.8.7 didn't help either, however the error is now reported
> > > > in
> > > > line 3467 (as opposed to 3468 before).
> > > >
> > > > And yes, the file does compile properly.
> > > > Are there any constructs (like strings containing '!' in the
> > > > source)
> > > > I could look out for?
> > > >
> > > > Regards,
> > > > Fabian
> > > >
> > > >
> > > >
> > > > ----- Original Message -----
> > > > > From: "Albert" < alb...@gm... >
> > > > > To: "Fabian Nick" < fab...@sc... >
> > > > > Cc: dox...@li...
> > > > > Sent: Tuesday, 13 May, 2014 12:55:10 PM
> > > > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468,
> > > > > state
> > > > > 4
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi Fabian,
> > > > >
> > > > > The line number is the number where it saw a problem and in
> > > > > this
> > > > > case
> > > > > this is when the file has been completely parsed.
> > > > > The state 4 means an error with SubprogBody, so something not
> > > > > ended
> > > > > properly (I assume the file compiles properly).
> > > > >
> > > > > You are using version 1.6.1 and the current version is 1.8.7 so
> > > > > an
> > > > > upgrade would certainly help.
> > > > > During the run does it say something about prepassing XX.f90 ?
> > > > > so like:
> > > > > Reading .../XX.f90
> > > > > Prepassing fixed form of .../XX.f90
> > > > > Parsing file XX.f90
> > > > >
> > > > > The line
> > > > > Prepassing fixed form of .../XX.f90
> > > > > should not be present, if present try to place a ! as fist line
> > > > > in
> > > > > the XX.f90 file.
> > > > >
> > > > >
> > > > > Anyhow upgrading to 1.8.7 is a very good idea.
> > > > >
> > > > >
> > > > > Albert
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, May 13, 2014 at 11:46 AM, Fabian Nick <
> > > > > fab...@sc... > wrote:
> > > > >
> > > > >
> > > > > Hi everyone,
> > > > >
> > > > > when trying to run doxygen on a large (Fortran-)project, I get
> > > > > the
> > > > > "Error in file XX.f90 line:3468, state 4" error. The
> > > > > interesting
> > > > > thing is that the file only has 3466 lines...
> > > > > The file is in fixed format. Somewhere on the web it was said
> > > > > that
> > > > > enabling the C-preprocessor might help but it doesn't in my
> > > > > case.
> > > > > I
> > > > > also read that there was a bug which was fixed in version 1.5.6
> > > > > (I
> > > > > think), however I'm using version 1.6.1.
> > > > >
> > > > > Any advice on what I could try?
> > > > >
> > > > > Regards,
> > > > > Fabian
> > > > >
> > > > >
> ------------------------------------------------------------------------------
> > > > > "Accelerate Dev Cycles with Automated Cross-Browser Testing -
> > > > > For
> > > > > FREE
> > > > > Instantly run your Selenium tests across 300+ browser/OS
> > > > > combos.
> > > > > Get unparalleled scalability from the best Selenium testing
> > > > > platform
> > > > > available
> > > > > Simple to use. Nothing to install. Get started now for free."
> > > > > http://p.sf.net/sfu/SauceLabs
> > > > > _______________________________________________
> > > > > Doxygen-users mailing list
> > > > > Dox...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
>

Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4

[Fabian N. <fab...@sc...>]

Sorry - right version, but wrong syntax...

----- Original Message -----
> From: "Albert" <alb...@gm...>
> To: "Fabian Nick" <fab...@sc...>
> Cc: dox...@li...
> Sent: Wednesday, 14 May, 2014 2:57:10 PM
> Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4
> 
> 
> 
> 
> Hi Fabian,
> 
> In which version of doxygen did you try the EXTENSION_MAPPING as it
> is new to version 1.8.7?
> 
> Albert
> 
> 
> 
> 
> On Wed, May 14, 2014 at 2:54 PM, Fabian Nick <
> fab...@sc... > wrote:
> 
> 
> Hi Albert,
> 
> thanks for your efforts.
> 
> Since the error only occured in one file, I think we can live with
> this quick fix for the time being.
> We'll have to see how our usage of Doxygen develops anyway. (Our code
> has grown over quite some years already so it won't be easy do
> document everything and have a nice and clean documentation)
> 
> Regarding the EXTENSION_MAPPING parameter: I tried setting it to
> FortranFree but the error still occured in the "non-fixed" version
> of the source file.
> 
> Best regards,
> 
> Fabian
> 
> ----- Original Message -----
> > From: "Albert" < alb...@gm... >
> > To: "Fabian Nick" < fab...@sc... >
> > Cc: dox...@li...
> 
> 
> > Sent: Tuesday, 13 May, 2014 7:56:38 PM
> > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state
> > 4
> > 
> > 
> > Posting on forum as well.
> > 
> > 
> > 
> > 
> > 
> > On Tue, May 13, 2014 at 7:46 PM, Albert < alb...@gm... >
> > wrote:
> > 
> > 
> > 
> > 
> > 
> > Hi Fabian,
> > 
> > I had a quick look.
> > 
> > In version 1.8.7 placing as first line"
> > !
> > 
> > i.e. a space followed by an exclamation mark solves the problem.
> > 
> > In version 1.6.1 the file is still preprocessed but the error is
> > gone
> > and the file looks OK (but maybe in more complex situations
> > problems
> > do occur).
> > 
> > 
> > Determination of free or fixed formatted code is not really
> > possible
> > there are always exceptions possible. In compilers this is often
> > solved by means of the extension and a switch. In doxygen 1.8.7 the
> > possibility exists to specify the type (free or fixed formatted)
> > Fortran code by means of EXTENSION_MAPPING in the Doxyfile:
> > # Doxygen selects the parser to use depending on the extension of
> > the
> > files it
> > # parses. With this tag you can assign which parser to use for a
> > given
> > # extension. Doxygen has a built-in mapping, but you can override
> > or
> > extend it
> > # using this tag. The format is ext=language, where ext is a file
> > extension, and
> > # language is one of the parsers supported by doxygen: IDL, Java,
> > Javascript,
> > # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format
> > Fortran:
> > # FortranFixed, free formatted Fortran: FortranFree, unknown
> > formatted Fortran:
> > # Fortran. In the later case the parser tries to guess whether the
> > code is fixed
> > # or free formatted code, this is the default for Fortran type
> > files), VHDL. For
> > # instance to make doxygen treat .inc files as Fortran files
> > (default
> > is PHP),
> > # and .f files as C (default is Fortran), use: inc=Fortran f=C.
> > #
> > # Note For files without extension you can use no_extension as a
> > placeholder.
> > #
> > # Note that for custom extensions you also need to set
> > FILE_PATTERNS
> > otherwise
> > # the files are not read by doxygen.
> > 
> > EXTENSION_MAPPING =
> > 
> > 
> > 
> > 
> > Albert
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On Tue, May 13, 2014 at 2:15 PM, Albert < alb...@gm... >
> > wrote:
> > 
> > 
> > 
> > 
> > 
> > Hi Fabian,
> > 
> > Very nice small example. I'll have a look in the evening.
> > 
> > Albert
> > 
> > (got message through both channels)
> > 
> > 
> > 
> > 
> > 
> > 
> > On Tue, May 13, 2014 at 1:42 PM, Fabian Nick <
> > fab...@sc... > wrote:
> > 
> > 
> > Hi Albert,
> > 
> > unfortunately I cannot send you the source file. However I was able
> > to boil it down to the one attached. For convenience, I also
> > attached the config file I used (it's just the one generated by
> > doxygen -g though...)
> > 
> > Notice the leading blanks.
> > The version attached does NOT work. However, if there are equally
> > many leading blanks before "subroutine testsub" and "end
> > subroutine"
> > it works!
> > Also, removing the module declarations helps as well.
> > 
> > If you need more information, just let me know!
> > 
> > Thanks,
> > 
> > Fabian
> > 
> > ----- Original Message -----
> > > From: "Albert" < alb...@gm... >
> > > To: "Fabian Nick" < fab...@sc... >
> > > Cc: dox...@li...
> > 
> > 
> > > Sent: Tuesday, 13 May, 2014 1:12:57 PM
> > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468,
> > > state
> > > 4
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Hi Fabian,
> > > 
> > > 
> > > It is always hard to find these kind of errors. What I do is that
> > > I
> > > reduce the file and see what happens (good old trial and error
> > > removing half of the file etc.).
> > > 
> > > Is it possible for you to post the file? (I could have a look in
> > > the
> > > evening.
> > > 
> > > Albert
> > > 
> > > 
> > > 
> > > 
> > > On Tue, May 13, 2014 at 1:07 PM, Fabian Nick <
> > > fab...@sc... > wrote:
> > > 
> > > 
> > > Hi Albert,
> > > 
> > > no the Prepassing line is not present. Just "preprocessing..."
> > > and
> > > "parsing..."
> > > I tried the extra line starting with "!" anyway, but it didn't
> > > help.
> > > 
> > > Using 1.8.7 didn't help either, however the error is now reported
> > > in
> > > line 3467 (as opposed to 3468 before).
> > > 
> > > And yes, the file does compile properly.
> > > Are there any constructs (like strings containing '!' in the
> > > source)
> > > I could look out for?
> > > 
> > > Regards,
> > > Fabian
> > > 
> > > 
> > > 
> > > ----- Original Message -----
> > > > From: "Albert" < alb...@gm... >
> > > > To: "Fabian Nick" < fab...@sc... >
> > > > Cc: dox...@li...
> > > > Sent: Tuesday, 13 May, 2014 12:55:10 PM
> > > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468,
> > > > state
> > > > 4
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Hi Fabian,
> > > > 
> > > > The line number is the number where it saw a problem and in
> > > > this
> > > > case
> > > > this is when the file has been completely parsed.
> > > > The state 4 means an error with SubprogBody, so something not
> > > > ended
> > > > properly (I assume the file compiles properly).
> > > > 
> > > > You are using version 1.6.1 and the current version is 1.8.7 so
> > > > an
> > > > upgrade would certainly help.
> > > > During the run does it say something about prepassing XX.f90 ?
> > > > so like:
> > > > Reading .../XX.f90
> > > > Prepassing fixed form of .../XX.f90
> > > > Parsing file XX.f90
> > > > 
> > > > The line
> > > > Prepassing fixed form of .../XX.f90
> > > > should not be present, if present try to place a ! as fist line
> > > > in
> > > > the XX.f90 file.
> > > > 
> > > > 
> > > > Anyhow upgrading to 1.8.7 is a very good idea.
> > > > 
> > > > 
> > > > Albert
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > On Tue, May 13, 2014 at 11:46 AM, Fabian Nick <
> > > > fab...@sc... > wrote:
> > > > 
> > > > 
> > > > Hi everyone,
> > > > 
> > > > when trying to run doxygen on a large (Fortran-)project, I get
> > > > the
> > > > "Error in file XX.f90 line:3468, state 4" error. The
> > > > interesting
> > > > thing is that the file only has 3466 lines...
> > > > The file is in fixed format. Somewhere on the web it was said
> > > > that
> > > > enabling the C-preprocessor might help but it doesn't in my
> > > > case.
> > > > I
> > > > also read that there was a bug which was fixed in version 1.5.6
> > > > (I
> > > > think), however I'm using version 1.6.1.
> > > > 
> > > > Any advice on what I could try?
> > > > 
> > > > Regards,
> > > > Fabian
> > > > 
> > > > ------------------------------------------------------------------------------
> > > > "Accelerate Dev Cycles with Automated Cross-Browser Testing -
> > > > For
> > > > FREE
> > > > Instantly run your Selenium tests across 300+ browser/OS
> > > > combos.
> > > > Get unparalleled scalability from the best Selenium testing
> > > > platform
> > > > available
> > > > Simple to use. Nothing to install. Get started now for free."
> > > > http://p.sf.net/sfu/SauceLabs
> > > > _______________________________________________
> > > > Doxygen-users mailing list
> > > > Dox...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> > > > 
> > > > 
> > > 
> > > 
> > 
> > 
> > 
> > 
> 
> 

Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4

[Albert <alb...@gm...>]

Hi Fabian,

In which version of doxygen did you try the EXTENSION_MAPPING as it is new
to version 1.8.7?

Albert


On Wed, May 14, 2014 at 2:54 PM, Fabian Nick <fab...@sc...
> wrote:

> Hi Albert,
>
> thanks for your efforts.
>
> Since the error only occured in one file, I think we can live with this
> quick fix for the time being.
> We'll have to see how our usage of Doxygen develops anyway. (Our code has
> grown over quite some years already so it won't be easy do document
> everything and have a nice and clean documentation)
>
> Regarding the EXTENSION_MAPPING parameter: I tried setting it to
> FortranFree but the error still occured in the "non-fixed" version of the
> source file.
>
> Best regards,
> Fabian
>
> ----- Original Message -----
> > From: "Albert" <alb...@gm...>
> > To: "Fabian Nick" <fab...@sc...>
> > Cc: dox...@li...
> > Sent: Tuesday, 13 May, 2014 7:56:38 PM
> > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4
> >
> >
> > Posting on forum as well.
> >
> >
> >
> >
> >
> > On Tue, May 13, 2014 at 7:46 PM, Albert < alb...@gm... >
> > wrote:
> >
> >
> >
> >
> >
> > Hi Fabian,
> >
> > I had a quick look.
> >
> > In version 1.8.7 placing as first line"
> > !
> >
> > i.e. a space followed by an exclamation mark solves the problem.
> >
> > In version 1.6.1 the file is still preprocessed but the error is gone
> > and the file looks OK (but maybe in more complex situations problems
> > do occur).
> >
> >
> > Determination of free or fixed formatted code is not really possible
> > there are always exceptions possible. In compilers this is often
> > solved by means of the extension and a switch. In doxygen 1.8.7 the
> > possibility exists to specify the type (free or fixed formatted)
> > Fortran code by means of EXTENSION_MAPPING in the Doxyfile:
> > # Doxygen selects the parser to use depending on the extension of the
> > files it
> > # parses. With this tag you can assign which parser to use for a
> > given
> > # extension. Doxygen has a built-in mapping, but you can override or
> > extend it
> > # using this tag. The format is ext=language, where ext is a file
> > extension, and
> > # language is one of the parsers supported by doxygen: IDL, Java,
> > Javascript,
> > # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format
> > Fortran:
> > # FortranFixed, free formatted Fortran: FortranFree, unknown
> > formatted Fortran:
> > # Fortran. In the later case the parser tries to guess whether the
> > code is fixed
> > # or free formatted code, this is the default for Fortran type
> > files), VHDL. For
> > # instance to make doxygen treat .inc files as Fortran files (default
> > is PHP),
> > # and .f files as C (default is Fortran), use: inc=Fortran f=C.
> > #
> > # Note For files without extension you can use no_extension as a
> > placeholder.
> > #
> > # Note that for custom extensions you also need to set FILE_PATTERNS
> > otherwise
> > # the files are not read by doxygen.
> >
> > EXTENSION_MAPPING =
> >
> >
> >
> >
> > Albert
> >
> >
> >
> >
> >
> >
> >
> > On Tue, May 13, 2014 at 2:15 PM, Albert < alb...@gm... >
> > wrote:
> >
> >
> >
> >
> >
> > Hi Fabian,
> >
> > Very nice small example. I'll have a look in the evening.
> >
> > Albert
> >
> > (got message through both channels)
> >
> >
> >
> >
> >
> >
> > On Tue, May 13, 2014 at 1:42 PM, Fabian Nick <
> > fab...@sc... > wrote:
> >
> >
> > Hi Albert,
> >
> > unfortunately I cannot send you the source file. However I was able
> > to boil it down to the one attached. For convenience, I also
> > attached the config file I used (it's just the one generated by
> > doxygen -g though...)
> >
> > Notice the leading blanks.
> > The version attached does NOT work. However, if there are equally
> > many leading blanks before "subroutine testsub" and "end subroutine"
> > it works!
> > Also, removing the module declarations helps as well.
> >
> > If you need more information, just let me know!
> >
> > Thanks,
> >
> > Fabian
> >
> > ----- Original Message -----
> > > From: "Albert" < alb...@gm... >
> > > To: "Fabian Nick" < fab...@sc... >
> > > Cc: dox...@li...
> >
> >
> > > Sent: Tuesday, 13 May, 2014 1:12:57 PM
> > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state
> > > 4
> > >
> > >
> > >
> > >
> > >
> > > Hi Fabian,
> > >
> > >
> > > It is always hard to find these kind of errors. What I do is that I
> > > reduce the file and see what happens (good old trial and error
> > > removing half of the file etc.).
> > >
> > > Is it possible for you to post the file? (I could have a look in
> > > the
> > > evening.
> > >
> > > Albert
> > >
> > >
> > >
> > >
> > > On Tue, May 13, 2014 at 1:07 PM, Fabian Nick <
> > > fab...@sc... > wrote:
> > >
> > >
> > > Hi Albert,
> > >
> > > no the Prepassing line is not present. Just "preprocessing..." and
> > > "parsing..."
> > > I tried the extra line starting with "!" anyway, but it didn't
> > > help.
> > >
> > > Using 1.8.7 didn't help either, however the error is now reported
> > > in
> > > line 3467 (as opposed to 3468 before).
> > >
> > > And yes, the file does compile properly.
> > > Are there any constructs (like strings containing '!' in the
> > > source)
> > > I could look out for?
> > >
> > > Regards,
> > > Fabian
> > >
> > >
> > >
> > > ----- Original Message -----
> > > > From: "Albert" < alb...@gm... >
> > > > To: "Fabian Nick" < fab...@sc... >
> > > > Cc: dox...@li...
> > > > Sent: Tuesday, 13 May, 2014 12:55:10 PM
> > > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468,
> > > > state
> > > > 4
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hi Fabian,
> > > >
> > > > The line number is the number where it saw a problem and in this
> > > > case
> > > > this is when the file has been completely parsed.
> > > > The state 4 means an error with SubprogBody, so something not
> > > > ended
> > > > properly (I assume the file compiles properly).
> > > >
> > > > You are using version 1.6.1 and the current version is 1.8.7 so
> > > > an
> > > > upgrade would certainly help.
> > > > During the run does it say something about prepassing XX.f90 ?
> > > > so like:
> > > > Reading .../XX.f90
> > > > Prepassing fixed form of .../XX.f90
> > > > Parsing file XX.f90
> > > >
> > > > The line
> > > > Prepassing fixed form of .../XX.f90
> > > > should not be present, if present try to place a ! as fist line
> > > > in
> > > > the XX.f90 file.
> > > >
> > > >
> > > > Anyhow upgrading to 1.8.7 is a very good idea.
> > > >
> > > >
> > > > Albert
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, May 13, 2014 at 11:46 AM, Fabian Nick <
> > > > fab...@sc... > wrote:
> > > >
> > > >
> > > > Hi everyone,
> > > >
> > > > when trying to run doxygen on a large (Fortran-)project, I get
> > > > the
> > > > "Error in file XX.f90 line:3468, state 4" error. The interesting
> > > > thing is that the file only has 3466 lines...
> > > > The file is in fixed format. Somewhere on the web it was said
> > > > that
> > > > enabling the C-preprocessor might help but it doesn't in my case.
> > > > I
> > > > also read that there was a bug which was fixed in version 1.5.6
> > > > (I
> > > > think), however I'm using version 1.6.1.
> > > >
> > > > Any advice on what I could try?
> > > >
> > > > Regards,
> > > > Fabian
> > > >
> > > >
> ------------------------------------------------------------------------------
> > > > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For
> > > > FREE
> > > > Instantly run your Selenium tests across 300+ browser/OS combos.
> > > > Get unparalleled scalability from the best Selenium testing
> > > > platform
> > > > available
> > > > Simple to use. Nothing to install. Get started now for free."
> > > > http://p.sf.net/sfu/SauceLabs
> > > > _______________________________________________
> > > > Doxygen-users mailing list
> > > > Dox...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> > > >
> > > >
> > >
> > >
> >
> >
> >
> >
>

Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4

[Fabian N. <fab...@sc...>]

Hi Albert,

thanks for your efforts.

Since the error only occured in one file, I think we can live with this quick fix for the time being.
We'll have to see how our usage of Doxygen develops anyway. (Our code has grown over quite some years already so it won't be easy do document everything and have a nice and clean documentation)

Regarding the EXTENSION_MAPPING parameter: I tried setting it to FortranFree but the error still occured in the "non-fixed" version of the source file.

Best regards,
Fabian

----- Original Message -----
> From: "Albert" <alb...@gm...>
> To: "Fabian Nick" <fab...@sc...>
> Cc: dox...@li...
> Sent: Tuesday, 13 May, 2014 7:56:38 PM
> Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4
> 
> 
> Posting on forum as well.
> 
> 
> 
> 
> 
> On Tue, May 13, 2014 at 7:46 PM, Albert < alb...@gm... >
> wrote:
> 
> 
> 
> 
> 
> Hi Fabian,
> 
> I had a quick look.
> 
> In version 1.8.7 placing as first line"
> !
> 
> i.e. a space followed by an exclamation mark solves the problem.
> 
> In version 1.6.1 the file is still preprocessed but the error is gone
> and the file looks OK (but maybe in more complex situations problems
> do occur).
> 
> 
> Determination of free or fixed formatted code is not really possible
> there are always exceptions possible. In compilers this is often
> solved by means of the extension and a switch. In doxygen 1.8.7 the
> possibility exists to specify the type (free or fixed formatted)
> Fortran code by means of EXTENSION_MAPPING in the Doxyfile:
> # Doxygen selects the parser to use depending on the extension of the
> files it
> # parses. With this tag you can assign which parser to use for a
> given
> # extension. Doxygen has a built-in mapping, but you can override or
> extend it
> # using this tag. The format is ext=language, where ext is a file
> extension, and
> # language is one of the parsers supported by doxygen: IDL, Java,
> Javascript,
> # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format
> Fortran:
> # FortranFixed, free formatted Fortran: FortranFree, unknown
> formatted Fortran:
> # Fortran. In the later case the parser tries to guess whether the
> code is fixed
> # or free formatted code, this is the default for Fortran type
> files), VHDL. For
> # instance to make doxygen treat .inc files as Fortran files (default
> is PHP),
> # and .f files as C (default is Fortran), use: inc=Fortran f=C.
> #
> # Note For files without extension you can use no_extension as a
> placeholder.
> #
> # Note that for custom extensions you also need to set FILE_PATTERNS
> otherwise
> # the files are not read by doxygen.
> 
> EXTENSION_MAPPING =
> 
> 
> 
> 
> Albert
> 
> 
> 
> 
> 
> 
> 
> On Tue, May 13, 2014 at 2:15 PM, Albert < alb...@gm... >
> wrote:
> 
> 
> 
> 
> 
> Hi Fabian,
> 
> Very nice small example. I'll have a look in the evening.
> 
> Albert
> 
> (got message through both channels)
> 
> 
> 
> 
> 
> 
> On Tue, May 13, 2014 at 1:42 PM, Fabian Nick <
> fab...@sc... > wrote:
> 
> 
> Hi Albert,
> 
> unfortunately I cannot send you the source file. However I was able
> to boil it down to the one attached. For convenience, I also
> attached the config file I used (it's just the one generated by
> doxygen -g though...)
> 
> Notice the leading blanks.
> The version attached does NOT work. However, if there are equally
> many leading blanks before "subroutine testsub" and "end subroutine"
> it works!
> Also, removing the module declarations helps as well.
> 
> If you need more information, just let me know!
> 
> Thanks,
> 
> Fabian
> 
> ----- Original Message -----
> > From: "Albert" < alb...@gm... >
> > To: "Fabian Nick" < fab...@sc... >
> > Cc: dox...@li...
> 
> 
> > Sent: Tuesday, 13 May, 2014 1:12:57 PM
> > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state
> > 4
> > 
> > 
> > 
> > 
> > 
> > Hi Fabian,
> > 
> > 
> > It is always hard to find these kind of errors. What I do is that I
> > reduce the file and see what happens (good old trial and error
> > removing half of the file etc.).
> > 
> > Is it possible for you to post the file? (I could have a look in
> > the
> > evening.
> > 
> > Albert
> > 
> > 
> > 
> > 
> > On Tue, May 13, 2014 at 1:07 PM, Fabian Nick <
> > fab...@sc... > wrote:
> > 
> > 
> > Hi Albert,
> > 
> > no the Prepassing line is not present. Just "preprocessing..." and
> > "parsing..."
> > I tried the extra line starting with "!" anyway, but it didn't
> > help.
> > 
> > Using 1.8.7 didn't help either, however the error is now reported
> > in
> > line 3467 (as opposed to 3468 before).
> > 
> > And yes, the file does compile properly.
> > Are there any constructs (like strings containing '!' in the
> > source)
> > I could look out for?
> > 
> > Regards,
> > Fabian
> > 
> > 
> > 
> > ----- Original Message -----
> > > From: "Albert" < alb...@gm... >
> > > To: "Fabian Nick" < fab...@sc... >
> > > Cc: dox...@li...
> > > Sent: Tuesday, 13 May, 2014 12:55:10 PM
> > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468,
> > > state
> > > 4
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Hi Fabian,
> > > 
> > > The line number is the number where it saw a problem and in this
> > > case
> > > this is when the file has been completely parsed.
> > > The state 4 means an error with SubprogBody, so something not
> > > ended
> > > properly (I assume the file compiles properly).
> > > 
> > > You are using version 1.6.1 and the current version is 1.8.7 so
> > > an
> > > upgrade would certainly help.
> > > During the run does it say something about prepassing XX.f90 ?
> > > so like:
> > > Reading .../XX.f90
> > > Prepassing fixed form of .../XX.f90
> > > Parsing file XX.f90
> > > 
> > > The line
> > > Prepassing fixed form of .../XX.f90
> > > should not be present, if present try to place a ! as fist line
> > > in
> > > the XX.f90 file.
> > > 
> > > 
> > > Anyhow upgrading to 1.8.7 is a very good idea.
> > > 
> > > 
> > > Albert
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > On Tue, May 13, 2014 at 11:46 AM, Fabian Nick <
> > > fab...@sc... > wrote:
> > > 
> > > 
> > > Hi everyone,
> > > 
> > > when trying to run doxygen on a large (Fortran-)project, I get
> > > the
> > > "Error in file XX.f90 line:3468, state 4" error. The interesting
> > > thing is that the file only has 3466 lines...
> > > The file is in fixed format. Somewhere on the web it was said
> > > that
> > > enabling the C-preprocessor might help but it doesn't in my case.
> > > I
> > > also read that there was a bug which was fixed in version 1.5.6
> > > (I
> > > think), however I'm using version 1.6.1.
> > > 
> > > Any advice on what I could try?
> > > 
> > > Regards,
> > > Fabian
> > > 
> > > ------------------------------------------------------------------------------
> > > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For
> > > FREE
> > > Instantly run your Selenium tests across 300+ browser/OS combos.
> > > Get unparalleled scalability from the best Selenium testing
> > > platform
> > > available
> > > Simple to use. Nothing to install. Get started now for free."
> > > http://p.sf.net/sfu/SauceLabs
> > > _______________________________________________
> > > Doxygen-users mailing list
> > > Dox...@li...
> > > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> > > 
> > > 
> > 
> > 
> 
> 
> 
> 

[Doxygen-users] @retval <return value> return "

[zero0d <daw...@ho...>]

HI,

I want to return this in <return value" -> * @retval "*+CSTT:
"APN","USER","PWD" OK*"

and get something like this +CSTT: ,APN",USER,PWD	OK".

What am I doing wrong?

Best Regards.




--
View this message in context: http://doxygen.10944.n7.nabble.com/retval-return-value-return-tp6644.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] Doxygen 1.8.7 OS X app crashes on launch (10.6.8)

[Dimitri v. H. <do...@gm...>]

Hi Stephen,

On 13 May 2014, at 21:47 , Stephen Greenfield <Ste...@sc...> wrote:
> 
> On 5/13/14 12:07 PM, "Dimitri van Heesch" <do...@gm...> wrote:
> 
> I did build doxywizard on MacOSX 10.9, but with -mmacosx-version-min=10.5.
> 
> I can't check myself if it works on earlier versions than 10.9. Maybe someone else can comment on this.
> You could also build doxygen yourself on 10.6.8. There is no reason it should not work.
> 
> 
> Thanks, Dimitri -- 
> 
> I was basing that on what someone posted on StackOverflow regarding this:
> 
> http://stackoverflow.com/questions/23614679/doxygen-os-x-app-crashes-on-launch-10-6-8
> 
> This is what they posted:
> 
> Doxywizard 1.8.7 and its library dependencies were built with a deployment target of 10.9:
> 
> otool -l Doxygen.app/Contents/MacOS/Doxywizard | fgrep --after-context=3 LC_VERSION_MIN
> cmd LC_VERSION_MIN_MACOSX
> cmdsize 16
> version 10.9
> sdk 10.9
> 
> This means the application can only be run on a system running OS X 10.9 or later. Either support for older operating systems was removed in this release or the binaries were accidentally built with an incorrect deployment target.
> 
> Where is the Xcode project to build the app that can be downloaded?

No, doxygen uses old Unix style ./configure scripts & Makefiles ;-)

The problem is most likely that I switched to a newer Qt version while migrating to Mavericks and this version 
didn't set the -mmacosx-version-min=10.5 explicitly, and then the default is to build for the latest greatest only (why Apple, why?)

The Doxygen package consists of the GUI (Doxygen.app/Contents/MacOS/Doxywizard) and the command line tool
(Doxygen.app/Contents/Resources/doxygen). The command line tool does work on 10.5 (as you can check with otool).

So while I figure out how to fix this, as a workaround you could also
- use the command line tool directly
- copy the latest doxygen command line tool over an older doxygen package where the wizard still works
  (then you won't be able to configure the most recently added options, but other than that you should be fine).

Regards,
  Dimitri

Re: [Doxygen-users] Doxygen 1.8.7 OS X app crashes on launch (10.6.8)

[Stephen G. <Ste...@sc...>]

On 5/13/14 12:07 PM, "Dimitri van Heesch" <do...@gm...<mailto:do...@gm...>> wrote:

I did build doxywizard on MacOSX 10.9, but with -mmacosx-version-min=10.5.

I can't check myself if it works on earlier versions than 10.9. Maybe someone else can comment on this.
You could also build doxygen yourself on 10.6.8. There is no reason it should not work.


Thanks, Dimitri --

I was basing that on what someone posted on StackOverflow regarding this:

http://stackoverflow.com/questions/23614679/doxygen-os-x-app-crashes-on-launch-10-6-8

This is what they posted:


Doxywizard 1.8.7 and its library dependencies were built with a deployment target of 10.9:

otool -l Doxygen.app/Contents/MacOS/Doxywizard | fgrep --after-context=3 LC_VERSION_MIN
cmd LC_VERSION_MIN_MACOSX
cmdsize 16
version 10.9
sdk 10.9


This means the application can only be run on a system running OS X 10.9 or later. Either support for older operating systems was removed in this release or the binaries were accidentally built with an incorrect deployment target.

Where is the Xcode project to build the app that can be downloaded?

Stephen

Re: [Doxygen-users] Doxygen 1.8.7 OS X app crashes on launch (10.6.8)

[Dimitri v. H. <do...@gm...>]

Hi Stephen,

I did build doxywizard on MacOSX 10.9, but with -mmacosx-version-min=10.5.

I can't check myself if it works on earlier versions than 10.9. Maybe someone else can comment on this.
You could also build doxygen yourself on 10.6.8. There is no reason it should not work.

Regards,
  Dimitri

On 13 May 2014, at 18:23 , Stephen Greenfield <Ste...@sc...> wrote:

> It appears the Doxywizard 1.8.7 was built with a minimum SDK of 10.9.  When double-click launching the app on 10.6.8, it crashes immediately with no backtrace:
> 
>  
> Process:         launchd [69602]
> Path:            /Applications/Doxygen.app/Contents/MacOS/Doxywizard
> Identifier:      org.doxygen
> Version:         ??? (???)
> Code Type:       X86 (Native)
> Parent Process:  launchd [125]
> 
> Date/Time:       2014-05-12 09:21:11.464 -0700
> OS Version:      Mac OS X 10.6.8 (10K549)
> Report Version:  6
> 
> Interval Since Last Report:          1152 sec
> Crashes Since Last Report:           2
> Per-App Crashes Since Last Report:   2
> 
> Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes: KERN_INVALID_ADDRESS at 0x000000008fe01030
> Crashed Thread:  Unknown
> 
> Backtrace not available
> 
> Unknown thread crashed with X86 Thread State (32-bit):
>   eax: 0x00000000  ebx: 0x00000000  ecx: 0x00000000  edx: 0x00000000
>   edi: 0x00000000  esi: 0x00000000  ebp: 0x00000000  esp: 0x00000000
>    ss: 0x0000001f  efl: 0x00010202  eip: 0x8fe01030   cs: 0x00000017
>    ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000000
>   cr2: 0x8fe01030
> 
> Binary images description not available
> 
> Any way around this without transferring code over to 10.9?
> 
> Stephen
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs_______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4

[Albert <alb...@gm...>]

Posting on forum as well.


On Tue, May 13, 2014 at 7:46 PM, Albert <alb...@gm...> wrote:

> Hi Fabian,
>
> I had a quick look.
> In version 1.8.7 placing as first line"
>  !
> i.e. a space followed by an exclamation mark solves the problem.
> In version 1.6.1 the file is still preprocessed but the error is gone and
> the file looks OK (but maybe in more complex situations problems do occur).
>
> Determination of free or fixed formatted code is not really possible there
> are always exceptions possible. In compilers this is often solved by means
> of the extension and a switch. In doxygen 1.8.7 the possibility exists to
> specify the type (free or fixed formatted) Fortran code by means of
> EXTENSION_MAPPING in the Doxyfile:
> # Doxygen selects the parser to use depending on the extension of the
> files it
> # parses. With this tag you can assign which parser to use for a given
> # extension. Doxygen has a built-in mapping, but you can override or
> extend it
> # using this tag. The format is ext=language, where ext is a file
> extension, and
> # language is one of the parsers supported by doxygen: IDL, Java,
> Javascript,
> # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
> # FortranFixed, free formatted Fortran: FortranFree, unknown formatted
> Fortran:
> # Fortran. In the later case the parser tries to guess whether the code is
> fixed
> # or free formatted code, this is the default for Fortran type files),
> VHDL. For
> # instance to make doxygen treat .inc files as Fortran files (default is
> PHP),
> # and .f files as C (default is Fortran), use: inc=Fortran f=C.
> #
> # Note For files without extension you can use no_extension as a
> placeholder.
> #
> # Note that for custom extensions you also need to set FILE_PATTERNS
> otherwise
> # the files are not read by doxygen.
>
> EXTENSION_MAPPING      =
>
>
>
> Albert
>
>
>
> On Tue, May 13, 2014 at 2:15 PM, Albert <alb...@gm...> wrote:
>
>> Hi Fabian,
>>
>> Very nice small example. I'll have a look in the evening.
>>
>> Albert
>>
>> (got message through both channels)
>>
>>
>> On Tue, May 13, 2014 at 1:42 PM, Fabian Nick <
>> fab...@sc...> wrote:
>>
>>> Hi Albert,
>>>
>>> unfortunately I cannot send you the source file. However I was able to
>>> boil it down to the one attached. For convenience, I also attached the
>>> config file I used (it's just the one generated by doxygen -g though...)
>>>
>>> Notice the leading blanks.
>>> The version attached does NOT work. However, if there are equally many
>>> leading blanks before "subroutine testsub" and "end subroutine" it works!
>>> Also, removing the module declarations helps as well.
>>>
>>> If you need more information, just let me know!
>>>
>>> Thanks,
>>> Fabian
>>>
>>> ----- Original Message -----
>>> > From: "Albert" <alb...@gm...>
>>> > To: "Fabian Nick" <fab...@sc...>
>>> > Cc: dox...@li...
>>> > Sent: Tuesday, 13 May, 2014 1:12:57 PM
>>> > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Hi Fabian,
>>> >
>>> >
>>> > It is always hard to find these kind of errors. What I do is that I
>>> > reduce the file and see what happens (good old trial and error
>>> > removing half of the file etc.).
>>> >
>>> > Is it possible for you to post the file? (I could have a look in the
>>> > evening.
>>> >
>>> > Albert
>>> >
>>> >
>>> >
>>> >
>>> > On Tue, May 13, 2014 at 1:07 PM, Fabian Nick <
>>> > fab...@sc... > wrote:
>>> >
>>> >
>>> > Hi Albert,
>>> >
>>> > no the Prepassing line is not present. Just "preprocessing..." and
>>> > "parsing..."
>>> > I tried the extra line starting with "!" anyway, but it didn't help.
>>> >
>>> > Using 1.8.7 didn't help either, however the error is now reported in
>>> > line 3467 (as opposed to 3468 before).
>>> >
>>> > And yes, the file does compile properly.
>>> > Are there any constructs (like strings containing '!' in the source)
>>> > I could look out for?
>>> >
>>> > Regards,
>>> > Fabian
>>> >
>>> >
>>> >
>>> > ----- Original Message -----
>>> > > From: "Albert" < alb...@gm... >
>>> > > To: "Fabian Nick" < fab...@sc... >
>>> > > Cc: dox...@li...
>>> > > Sent: Tuesday, 13 May, 2014 12:55:10 PM
>>> > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state
>>> > > 4
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > Hi Fabian,
>>> > >
>>> > > The line number is the number where it saw a problem and in this
>>> > > case
>>> > > this is when the file has been completely parsed.
>>> > > The state 4 means an error with SubprogBody, so something not ended
>>> > > properly (I assume the file compiles properly).
>>> > >
>>> > > You are using version 1.6.1 and the current version is 1.8.7 so an
>>> > > upgrade would certainly help.
>>> > > During the run does it say something about prepassing XX.f90 ?
>>> > > so like:
>>> > > Reading .../XX.f90
>>> > > Prepassing fixed form of .../XX.f90
>>> > > Parsing file XX.f90
>>> > >
>>> > > The line
>>> > > Prepassing fixed form of .../XX.f90
>>> > > should not be present, if present try to place a ! as fist line in
>>> > > the XX.f90 file.
>>> > >
>>> > >
>>> > > Anyhow upgrading to 1.8.7 is a very good idea.
>>> > >
>>> > >
>>> > > Albert
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > On Tue, May 13, 2014 at 11:46 AM, Fabian Nick <
>>> > > fab...@sc... > wrote:
>>> > >
>>> > >
>>> > > Hi everyone,
>>> > >
>>> > > when trying to run doxygen on a large (Fortran-)project, I get the
>>> > > "Error in file XX.f90 line:3468, state 4" error. The interesting
>>> > > thing is that the file only has 3466 lines...
>>> > > The file is in fixed format. Somewhere on the web it was said that
>>> > > enabling the C-preprocessor might help but it doesn't in my case. I
>>> > > also read that there was a bug which was fixed in version 1.5.6 (I
>>> > > think), however I'm using version 1.6.1.
>>> > >
>>> > > Any advice on what I could try?
>>> > >
>>> > > Regards,
>>> > > Fabian
>>> > >
>>> > >
>>> ------------------------------------------------------------------------------
>>> > > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For
>>> > > FREE
>>> > > Instantly run your Selenium tests across 300+ browser/OS combos.
>>> > > Get unparalleled scalability from the best Selenium testing
>>> > > platform
>>> > > available
>>> > > Simple to use. Nothing to install. Get started now for free."
>>> > > http://p.sf.net/sfu/SauceLabs
>>> > > _______________________________________________
>>> > > Doxygen-users mailing list
>>> > > Dox...@li...
>>> > > https://lists.sourceforge.net/lists/listinfo/doxygen-users
>>> > >
>>> > >
>>> >
>>> >
>>>
>>
>>
>

[Doxygen-users] Doxygen 1.8.7 OS X app crashes on launch (10.6.8)

[Stephen G. <Ste...@sc...>]

It appears the Doxywizard 1.8.7 was built with a minimum SDK of 10.9.  When double-click launching the app on 10.6.8, it crashes immediately with no backtrace:


Process:         launchd [69602]
Path:            /Applications/Doxygen.app/Contents/MacOS/Doxywizard
Identifier:      org.doxygen
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [125]

Date/Time:       2014-05-12 09:21:11.464 -0700
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version:  6

Interval Since Last Report:          1152 sec
Crashes Since Last Report:           2
Per-App Crashes Since Last Report:   2

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000008fe01030
Crashed Thread:  Unknown

Backtrace not available

Unknown thread crashed with X86 Thread State (32-bit):
  eax: 0x00000000  ebx: 0x00000000  ecx: 0x00000000  edx: 0x00000000
  edi: 0x00000000  esi: 0x00000000  ebp: 0x00000000  esp: 0x00000000
   ss: 0x0000001f  efl: 0x00010202  eip: 0x8fe01030   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000000
  cr2: 0x8fe01030

Binary images description not available

Any way around this without transferring code over to 10.9?

Stephen

[Doxygen-users] Limit width in dot diagrams

[ardoster <em...@rb...>]

Hi

I'm trying to limit the width size of diagrams generated by Dot. I've read
that Doxygen "tries" to limit this size to 1024 px, although I'm getting
images even bigger. How could I configure this value?

There's no option to limit this size?

Thanks in advance

Regards,





--
View this message in context: http://doxygen.10944.n7.nabble.com/Limit-width-in-dot-diagrams-tp6638.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4

[Albert <alb...@gm...>]

Hi Fabian,

Very nice small example. I'll have a look in the evening.

Albert

(got message through both channels)


On Tue, May 13, 2014 at 1:42 PM, Fabian Nick <fab...@sc...
> wrote:

> Hi Albert,
>
> unfortunately I cannot send you the source file. However I was able to
> boil it down to the one attached. For convenience, I also attached the
> config file I used (it's just the one generated by doxygen -g though...)
>
> Notice the leading blanks.
> The version attached does NOT work. However, if there are equally many
> leading blanks before "subroutine testsub" and "end subroutine" it works!
> Also, removing the module declarations helps as well.
>
> If you need more information, just let me know!
>
> Thanks,
> Fabian
>
> ----- Original Message -----
> > From: "Albert" <alb...@gm...>
> > To: "Fabian Nick" <fab...@sc...>
> > Cc: dox...@li...
> > Sent: Tuesday, 13 May, 2014 1:12:57 PM
> > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4
> >
> >
> >
> >
> >
> > Hi Fabian,
> >
> >
> > It is always hard to find these kind of errors. What I do is that I
> > reduce the file and see what happens (good old trial and error
> > removing half of the file etc.).
> >
> > Is it possible for you to post the file? (I could have a look in the
> > evening.
> >
> > Albert
> >
> >
> >
> >
> > On Tue, May 13, 2014 at 1:07 PM, Fabian Nick <
> > fab...@sc... > wrote:
> >
> >
> > Hi Albert,
> >
> > no the Prepassing line is not present. Just "preprocessing..." and
> > "parsing..."
> > I tried the extra line starting with "!" anyway, but it didn't help.
> >
> > Using 1.8.7 didn't help either, however the error is now reported in
> > line 3467 (as opposed to 3468 before).
> >
> > And yes, the file does compile properly.
> > Are there any constructs (like strings containing '!' in the source)
> > I could look out for?
> >
> > Regards,
> > Fabian
> >
> >
> >
> > ----- Original Message -----
> > > From: "Albert" < alb...@gm... >
> > > To: "Fabian Nick" < fab...@sc... >
> > > Cc: dox...@li...
> > > Sent: Tuesday, 13 May, 2014 12:55:10 PM
> > > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state
> > > 4
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hi Fabian,
> > >
> > > The line number is the number where it saw a problem and in this
> > > case
> > > this is when the file has been completely parsed.
> > > The state 4 means an error with SubprogBody, so something not ended
> > > properly (I assume the file compiles properly).
> > >
> > > You are using version 1.6.1 and the current version is 1.8.7 so an
> > > upgrade would certainly help.
> > > During the run does it say something about prepassing XX.f90 ?
> > > so like:
> > > Reading .../XX.f90
> > > Prepassing fixed form of .../XX.f90
> > > Parsing file XX.f90
> > >
> > > The line
> > > Prepassing fixed form of .../XX.f90
> > > should not be present, if present try to place a ! as fist line in
> > > the XX.f90 file.
> > >
> > >
> > > Anyhow upgrading to 1.8.7 is a very good idea.
> > >
> > >
> > > Albert
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Tue, May 13, 2014 at 11:46 AM, Fabian Nick <
> > > fab...@sc... > wrote:
> > >
> > >
> > > Hi everyone,
> > >
> > > when trying to run doxygen on a large (Fortran-)project, I get the
> > > "Error in file XX.f90 line:3468, state 4" error. The interesting
> > > thing is that the file only has 3466 lines...
> > > The file is in fixed format. Somewhere on the web it was said that
> > > enabling the C-preprocessor might help but it doesn't in my case. I
> > > also read that there was a bug which was fixed in version 1.5.6 (I
> > > think), however I'm using version 1.6.1.
> > >
> > > Any advice on what I could try?
> > >
> > > Regards,
> > > Fabian
> > >
> > >
> ------------------------------------------------------------------------------
> > > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For
> > > FREE
> > > Instantly run your Selenium tests across 300+ browser/OS combos.
> > > Get unparalleled scalability from the best Selenium testing
> > > platform
> > > available
> > > Simple to use. Nothing to install. Get started now for free."
> > > http://p.sf.net/sfu/SauceLabs
> > > _______________________________________________
> > > Doxygen-users mailing list
> > > Dox...@li...
> > > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> > >
> > >
> >
> >
>

Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4

[Albert <alb...@gm...>]

Hi Fabian,

It is always hard to find these kind of errors. What I do is that I reduce
the file and see what happens (good old trial and error removing half of
the file etc.).

Is it possible for you to post the file? (I could have a look in the
evening.

Albert


On Tue, May 13, 2014 at 1:07 PM, Fabian Nick <fab...@sc...
> wrote:

> Hi Albert,
>
> no the Prepassing line is not present. Just "preprocessing..." and
> "parsing..."
> I tried the extra line starting with "!" anyway, but it didn't help.
>
> Using 1.8.7 didn't help either, however the error is now reported in line
> 3467 (as opposed to 3468 before).
>
> And yes, the file does compile properly.
> Are there any constructs (like strings containing '!' in the source) I
> could look out for?
>
> Regards,
> Fabian
>
> ----- Original Message -----
> > From: "Albert" <alb...@gm...>
> > To: "Fabian Nick" <fab...@sc...>
> > Cc: dox...@li...
> > Sent: Tuesday, 13 May, 2014 12:55:10 PM
> > Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Fabian,
> >
> > The line number is the number where it saw a problem and in this case
> > this is when the file has been completely parsed.
> > The state 4 means an error with SubprogBody, so something not ended
> > properly (I assume the file compiles properly).
> >
> > You are using version 1.6.1 and the current version is 1.8.7 so an
> > upgrade would certainly help.
> > During the run does it say something about prepassing XX.f90 ?
> > so like:
> > Reading .../XX.f90
> > Prepassing fixed form of .../XX.f90
> > Parsing file XX.f90
> >
> > The line
> > Prepassing fixed form of .../XX.f90
> > should not be present, if present try to place a ! as fist line in
> > the XX.f90 file.
> >
> >
> > Anyhow upgrading to 1.8.7 is a very good idea.
> >
> >
> > Albert
> >
> >
> >
> >
> >
> >
> >
> > On Tue, May 13, 2014 at 11:46 AM, Fabian Nick <
> > fab...@sc... > wrote:
> >
> >
> > Hi everyone,
> >
> > when trying to run doxygen on a large (Fortran-)project, I get the
> > "Error in file XX.f90 line:3468, state 4" error. The interesting
> > thing is that the file only has 3466 lines...
> > The file is in fixed format. Somewhere on the web it was said that
> > enabling the C-preprocessor might help but it doesn't in my case. I
> > also read that there was a bug which was fixed in version 1.5.6 (I
> > think), however I'm using version 1.6.1.
> >
> > Any advice on what I could try?
> >
> > Regards,
> > Fabian
> >
> >
> ------------------------------------------------------------------------------
> > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For
> > FREE
> > Instantly run your Selenium tests across 300+ browser/OS combos.
> > Get unparalleled scalability from the best Selenium testing platform
> > available
> > Simple to use. Nothing to install. Get started now for free."
> > http://p.sf.net/sfu/SauceLabs
> > _______________________________________________
> > Doxygen-users mailing list
> > Dox...@li...
> > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> >
> >
>

Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4

[Fabian N. <fab...@sc...>]

Hi Albert,

no the Prepassing line is not present. Just "preprocessing..." and "parsing..."
I tried the extra line starting with "!" anyway, but it didn't help.

Using 1.8.7 didn't help either, however the error is now reported in line 3467 (as opposed to 3468 before).

And yes, the file does compile properly.
Are there any constructs (like strings containing '!' in the source) I could look out for?

Regards,
Fabian

----- Original Message -----
> From: "Albert" <alb...@gm...>
> To: "Fabian Nick" <fab...@sc...>
> Cc: dox...@li...
> Sent: Tuesday, 13 May, 2014 12:55:10 PM
> Subject: Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4
> 
> 
> 
> 
> 
> 
> 
> 
> Hi Fabian,
> 
> The line number is the number where it saw a problem and in this case
> this is when the file has been completely parsed.
> The state 4 means an error with SubprogBody, so something not ended
> properly (I assume the file compiles properly).
> 
> You are using version 1.6.1 and the current version is 1.8.7 so an
> upgrade would certainly help.
> During the run does it say something about prepassing XX.f90 ?
> so like:
> Reading .../XX.f90
> Prepassing fixed form of .../XX.f90
> Parsing file XX.f90
> 
> The line
> Prepassing fixed form of .../XX.f90
> should not be present, if present try to place a ! as fist line in
> the XX.f90 file.
> 
> 
> Anyhow upgrading to 1.8.7 is a very good idea.
> 
> 
> Albert
> 
> 
> 
> 
> 
> 
> 
> On Tue, May 13, 2014 at 11:46 AM, Fabian Nick <
> fab...@sc... > wrote:
> 
> 
> Hi everyone,
> 
> when trying to run doxygen on a large (Fortran-)project, I get the
> "Error in file XX.f90 line:3468, state 4" error. The interesting
> thing is that the file only has 3466 lines...
> The file is in fixed format. Somewhere on the web it was said that
> enabling the C-preprocessor might help but it doesn't in my case. I
> also read that there was a bug which was fixed in version 1.5.6 (I
> think), however I'm using version 1.6.1.
> 
> Any advice on what I could try?
> 
> Regards,
> Fabian
> 
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For
> FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
> 
>