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 663642 - doxygen SEGV building ruby
doxygen SEGV building ruby
Status: RESOLVED DUPLICATE of bug 662044
Product: doxygen
Classification: Other
Component: general
1.7.5.1
Other Solaris
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-11-08 17:34 UTC by Rainer Orth
Modified: 2011-11-08 19:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rainer Orth 2011-11-08 17:34:47 UTC
When building ruby 1.9.2 on Solaris 10 (both SPARC and x86), I hit a SEGV late
in the build.  It turned out that it is doxygen that SEGVs, independent of using
Studio CC or g++.

I've rebuilt doxygen with g++ 4.6 -g3 -O0 to simplify debugging and find this stacktrace:

  • #0 strlen
    from /lib/libc.so.1
  • #1 _ndoprnt
    from /lib/libc.so.1
  • #2 vfprintf
    from /lib/libc.so.1
  • #3 msg
    at message.cpp line 111
  • #4 FileDef::acquireFileVersion
    at filedef.cpp line 1519
  • #5 FileDef::FileDef
    at filedef.cpp line 100
  • #6 readDir
    at doxygen.cpp line 9067
  • #7 readFileOrDirectory
    at doxygen.cpp line 9188
  • #8 searchInputFiles
    at doxygen.cpp line 10079
  • #9 parseInput
    at doxygen.cpp line 10321
  • #10 main
    at main.cpp line 37

strlen usually SEGVs if called with a NULL pointer.

Looking at the code in src/message.cpp (msg), it seems that you are trying
to access the arguments of a variadic function as a va_list, which AFAIK
cannot be done at all, not only not in a portable way.
Comment 1 Dimitri van Heesch 2011-11-08 19:01:01 UTC
This looks to be a duplicate. 
The fix should already be available in the latest SVN update.

*** This bug has been marked as a duplicate of bug 662044 ***