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 723314 - Doxygen crashes on incorrect end group /**< @} */
Doxygen crashes on incorrect end group /**< @} */
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.6
Other Windows
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-01-30 20:12 UTC by dandev37
Modified: 2014-04-21 10:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description dandev37 2014-01-30 20:12:23 UTC
I have run into an issue where doxygen crashes on an *incorrectly* formatted doxygen tag within a source file instead of providing the user with a helpful error message.  See code below to reproduce the issue with doxygen release v1.8.6, on Windows 7.

/**
 * @file file.c
 * 
 * @addtogroup SomeGroup
 * @{
 */

/**
 * Some function.
 */
void	someFunction( void )
{
}

/**< @} */

Note the incorrect addition of the less than ("<") symbol causes doxygen to crash.

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	doxygen.exe
  Application Version:	0.0.0.0
  Application Timestamp:	52b9cc74
  Fault Module Name:	doxygen.exe
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	52b9cc74
  Exception Code:	c0000005
  Exception Offset:	000000000018801f
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	4105
  Additional Information 1:	d13f
  Additional Information 2:	d13f983471b1fc894b4a912a00edd2b8
  Additional Information 3:	6acc
  Additional Information 4:	6acc7bd8799c565455f744451906a0f3
Comment 1 Dimitri van Heesch 2014-02-03 20:04:14 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 2 Dimitri van Heesch 2014-04-21 10:09:12 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.7. 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 (preferrably in the form of a self-contained example).