Found a fix for bug 356399

Hi All,
Hi Dimitri,

I'm completely new to Doxygen development but since I had a couple of  
problems on my own doxygen-based documentation build system, I found  
at least an answer for one !

I encountered bug 356399 (http://bugzilla.gnome.org/show_activity.cgi? 
id=356399) and traced it down on my MacBook. Here was the kind of  
message I had:

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

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

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

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

Here is my patch:

Index: src/tagreader.cpp
===================================================================
--- src/tagreader.cpp   (revision 590)
+++ src/tagreader.cpp   (working copy)
@@ -237,14 +237,16 @@
        m_inputFileName = 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 = "";
===================================================================

My 2 cents, hope this helps !

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

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

Best regards,
-- 
Maurice Elallouf





-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/