Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7178

Regular expression of Doxygen parser is too complex for JDK pattern

    XMLWordPrintable

Details

    • warnings-ng 4.0.0, analysis-model-api 3.0.0

    Description

      The Hudson Warnings pluging crash when checking warnings during build. See attached crash dump file.
      Hudson version is 1.370. Warnings Plug-in version is 3.8, In general Hudson and it's plugings are up to date.
      In general we are running all jobs in slave computers. I think, when the Warnings pluging 3.8 was installed this crash occurred.
      When this same Warnings pluging is running on Windows environment, it doesn't crash.

      Attachments

        Issue Links

          Activity

            drulli Ulli Hafner added a comment -

            Can someone please check if Jenkins running on JDK 7 solves this problem?

            drulli Ulli Hafner added a comment - Can someone please check if Jenkins running on JDK 7 solves this problem?

            FreeBSD 9.1, OpenJDK 7. Same thing - getting java.lang.stackoverflow when trying to process Doxygen logs.

            kworr Volodymyr Kostyrko added a comment - FreeBSD 9.1, OpenJDK 7. Same thing - getting java.lang.stackoverflow when trying to process Doxygen logs.
            drulli Ulli Hafner added a comment -

            Ok, thanks for checking. I think the doxygen parser needs to be re-written in order to avoid that JDK bug.

            drulli Ulli Hafner added a comment - Ok, thanks for checking. I think the doxygen parser needs to be re-written in order to avoid that JDK bug.
            julrich Jochen Ulrich added a comment -

            This issue seems to be related to the size of the log (see also this comment in the linked ticket).
            So there is a simple workaround: capture the stderr output of Doxygen in a file (or use the WARN_LOGFILE parameter in the Doxyfile) and let the warnings plugin run on that file.

            julrich Jochen Ulrich added a comment - This issue seems to be related to the size of the log (see also this comment in the linked ticket ). So there is a simple workaround: capture the stderr output of Doxygen in a file (or use the WARN_LOGFILE parameter in the Doxyfile) and let the warnings plugin run on that file.
            drulli Ulli Hafner added a comment -

            It would make sense to re-implement the parser.

            drulli Ulli Hafner added a comment - It would make sense to re-implement the parser.

            People

              Unassigned Unassigned
              tapiomtr tapiomtr
              Votes:
              6 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: