Hi Dimitri, > I think I found the problem. Resource::data was used directly as a string, > but it is not \0 terminated! > I've just pushed the following change to address this, which also makes the > ResourceMgr::get() method private > so it cannot be (ab)used like this anymore. > > https://github.com/doxygen/doxygen/commit/15a87a623791bf407b3076960cdd1133c8973357
Thanks, that patch respectively the latest development version of doxygen lets the "strange" line vanish. And for completeness: I use doxygen under Linux (not Windows) and as Albert mentioned with SOURCE_BROWSER and SOURCE_TOOLTIPS set to YES. Regards, Jens >> On 31 Aug 2015, at 19:01 , Albert <albert.te...@gmail.com> wrote: >> >> Jens, >> >> I tried to reproduce the problem (on windows) with the current head and was >> not successful. >> The htmlgen.cpp had no changes related to dynsections.js in the relevant >> part (mentioned lines 731 - 756) in the mentioned period and the template >> dynsections.js has never been changed since its introduction in that >> directory (November 13, 2014). >> >> By default the dynsections.js is 97 lines long and when setting >> SOURCE_BROWSER and SOURCE_TOOLTIPS to YES the code is extended by the lines >> specified in htmlgen.cpp. These lines are just "pasted" and don't contain >> special characters. >> >> Albert >> >> On Mon, Aug 31, 2015 at 5:22 PM, Schleusener, Jens >> <jens.schleuse...@t-online.de> wrote: >> Hi, >> >> since 2th June 2015 appears in the output file dynsections.js a new line >> that appears at least to me as layman a little bit strange. >> >> The output file dynsections.js seems to be primarly contain the static >> contents of the file ./doxygen/templates/html/dynsections.js maybe >> complemented by the JavaScript code generated by the lines 731-756 of >> doxygen/src/htmlgen.cpp. >> >> Just between this both code segments there is now at line 98 (at least in >> my applications of the current development version of Doxygen) a line >> containing the hex code 440C (ASCII: D + Formfeed). >> >> Is that the expected behaviour or possibly a small error? >> >> Sorry for the a little bit unprofessional problem description. >> >> Regards >> >> Jens >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Doxygen-users mailing list >> Doxygen-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/doxygen-users >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Doxygen-users mailing list >> Doxygen-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/doxygen-users > > ------------------------------------------------------------------------------ _______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
