After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 608590 - *** buffer overflow detected ***: doxygen terminated
*** buffer overflow detected ***: doxygen terminated
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.6.1
Other Linux
: Normal critical
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-01-31 12:40 UTC by Aleksey
Modified: 2010-02-21 12:57 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
small example demonstrating the problem (160.00 KB, application/x-tar)
2010-01-31 12:40 UTC, Aleksey 		Details

Description Aleksey 2010-01-31 12:40:32 UTC 
Created attachment 152671 [details]
small example demonstrating the problem

I'm running doxygen on our sources in C++ which include this statement (in russian):

"/// \class некорректное имя класса на русском языке"

and program is crashing with message:

"*** buffer overflow detected ***: doxygen terminated"

I know this statement is incorrect, but program must operate with any input data correctly.

The windows version of doxygen has the same problem.

OS: Ubuntu Netbook Remix 9.10, kernel version 2.6.31-17
    Windows XP Home Edition

I'm sorry for my English.
Comment 1 Dimitri van Heesch 2010-02-01 09:00:41 UTC 
Hi Aleksey, I will look into this bug, but one thing I noticed is that 
you use \class in the wrong way. The \class command should be followed by a 
class name (which cannot be a Russian word in C++).
Comment 2 Dimitri van Heesch 2010-02-01 22:11:04 UTC 
Should be fixed in the next subversion update.
Comment 3 Aleksey 2010-02-02 21:09:24 UTC 
Thank you very much. Doxygen is the great program.
Comment 4 Dimitri van Heesch 2010-02-21 12:57:38 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.3. 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.