doxygen-develop

[Doxygen-develop] ExtCmd debug information disabled in portable_system

[Olivier C. <ocr...@fr...>]

Hi

I am having a hard time tracking down the following messages in a very big
project:

Error: Problems running epstopdf. Check your TeX installation!
epstopdf: The input file does not exist.

I need to know what Doxygen wants epstopdf to do.

The ExtCmd debugging would be very helpful for that.

Unfortunately, the corresponding line:
Debug::print(Debug::ExtCmd,0,"Executing external command %s`\n",fullCmd.data());

has been commented out in the body of portable_system() with this commit:

    Revision 578
    Modified Sun Sep 2 19:15:32 2007 UTC (7 weeks, 1 day ago) by dimitri
    File length: 8962 byte(s)

    Release-1.5.3-20070902

Is there any reason for that?
I really miss this debug information!

Thanks for your help.

Regards
-- 
Olivier

Re: [Doxygen-develop] ExtCmd debug information disabled in portable_system

[Olivier C. <ocr...@fr...>]

Hi

Actually, this debug information is available only if NODEBUG is not set.

It seems the official version is compiled with NODEBUG. I think it's not a good
idea, since prohibits debugging possibilities and bug reports from the users.

I spent because of that a very long time to find out what the following error
messages were about:
Error: Problems running epstopdf. Check your TeX installation!
epstopdf: The input file does not exist.
(with no other information)

Would it be possible to enable the debug (when using the -d switch) in the
releases?

Regards

Olivier

Re: [Doxygen-develop] ExtCmd debug information disabled in portable_system

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

On 10/24/07, Olivier Croquette <ocr...@fr...> wrote:
>
> Hi
>
> Actually, this debug information is available only if NODEBUG is not set.
>
> It seems the official version is compiled with NODEBUG. I think it's not a
> good
> idea, since prohibits debugging possibilities and bug reports from the
> users.



No the official version (1.5.3) still had the code with the command
commented out
(see
http://svn.planetsaphire.com/viewvc.cgi/trunk/src/portable.cpp?root=doxygen&r1=566&r2=578
)
I need the NODEBUG flag for doxywizard, which also uses portable.cpp but not
the
debug mechanism (that's why I commented it out earlier).

I spent because of that a very long time to find out what the following
> error
> messages were about:
> Error: Problems running epstopdf. Check your TeX installation!
> epstopdf: The input file does not exist.
> (with no other information)
>
> Would it be possible to enable the debug (when using the -d switch) in the
> releases?


Sure, it will work in the next release (and already in the latest SVN
release as well).

Regards,
  Dimitri

[Doxygen-develop] Found a fix for bug 356399

[Maurice E. <mel...@fr...>]

Hi All,
Hi Dimitri,

I'm completely new to Doxygen development but since I had a couple of =20=

problems on my own doxygen-based documentation build system, I found =20
at least an answer for one !

I encountered bug 356399 (http://bugzilla.gnome.org/show_activity.cgi?=20=

id=3D356399) and traced it down on my MacBook. Here was the kind of =20
message I had:

	path/to/my/tagfile.tag:63: Duplicate anchor \240\241\225=01 =
found

It took me a couple of hours to setup a Xcode project around doxygen =20
source code (if anybody is interested ?) so that I can reproduce =20
exactly my own documentation build system runtime constraints =20
(doxygen being part of a whole), therefore I did not spend too much =20
time to try to reduce the problem.

Anyway... this bug is due to the fact that va_args is stacked twice, =20
once in TagFileParser::warn, then again in ::warn  (in message.cpp). =20
I've found a quick patch by creating 2 overloaded prototypes for =20
TagFileParser::warn, corresponding to their current use.

Another solution would be to make the do_warn routine available =20
outside of message.cpp.

Here is my patch:

Index: src/tagreader.cpp
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- src/tagreader.cpp   (revision 590)
+++ src/tagreader.cpp   (working copy)
@@ -237,14 +237,16 @@
        m_inputFileName =3D fileName;
      }

-    void warn(const char *fmt,...)
+    void warn(const char *fmt)
      {
-      va_list args;
-      va_start(args, fmt);
-      ::warn(m_inputFileName,m_locator->lineNumber(),fmt,args);
-      va_end(args);
+      ::warn(m_inputFileName,m_locator->lineNumber(),fmt);
      }

+    void warn(const char *fmt, const char * s)
+    {
+      ::warn(m_inputFileName,m_locator->lineNumber(),fmt,s);
+    }
+
      void startCompound( const QXmlAttributes& attrib )
      {
        m_curString =3D "";
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

My 2 cents, hope this helps !

It helped me as well, since I found that my error was only caused by =20
a duplicate tag file in my TAGFILES list ;-/

I'm still in the process of registering for Bugzilla access so I did =20
not submit my comments/resolution there yet.

Best regards,
--=20
Maurice Elallouf