Thread: [Doxygen-users] Crash using Doxygen 1.8.13
Brought to you by:
dimitri
From: Vinnie F. <vin...@gm...> - 2017-04-23 18:11:37
|
My documentation builds correctly with 1.8.12 but when I try 1.8.13 I get a segmentation fault. The project is located here: https://github.com/vinniefalco/Beast To reproduce the steps, issue these commands from the root of the local repository: cd doc ./makeqbk.sh Result: When Doxygen 1.8.13 is invoked, it will do some processing and then terminate with a segmentation fault. Please advise |
From: Dimitri v. H. <do...@gm...> - 2017-04-23 18:50:37
|
Hi Vinnie, Looks like the issue is already fixed in the latest version from Github. Regards, Dimitri > On 23 Apr 2017, at 20:11 , Vinnie Falco <vin...@gm...> wrote: > > My documentation builds correctly with 1.8.12 but when I try 1.8.13 I > get a segmentation fault. > > The project is located here: > https://github.com/vinniefalco/Beast > > To reproduce the steps, issue these commands from the root of the > local repository: > > cd doc > ./makeqbk.sh > > Result: When Doxygen 1.8.13 is invoked, it will do some processing and > then terminate with a segmentation fault. > > Please advise > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users |
From: L A W. <do...@tl...> - 2017-04-25 07:49:42
|
Dimitri van Heesch wrote: > Hi Vinnie, > > Looks like the issue is already fixed in the latest version from Github. > > Regards, > Dimitri > ---- Is it? Is it the same as this bug reported against 1.8.13 here: https://bugzilla.gnome.org/show_bug.cgi?id=781306 No one ever responded to it after I uploaded the requested information (and no way to change status from 'NEEDINFO' to 'OPEN'...)... |
From: Vinnie F. <vin...@gm...> - 2017-04-25 15:10:24
|
On Tue, Apr 25, 2017 at 12:49 AM, L A Walsh <do...@tl...> wrote: > Dimitri van Heesch wrote: >> Looks like the issue is already fixed in the latest version from Github. It should be easy to verify, just clone my repository and execute the 2 steps I provided. Did the Beast documentation build for you? |
From: Vinnie F. <vin...@gm...> - 2017-04-25 19:00:30
|
On Tue, Apr 25, 2017 at 11:57 AM, L A Walsh <do...@tl...> wrote: > ?? Beast? ?? > For me it was a different project. > > From what I understand, different files are included in the > git-version than come in the tarball. might > that not change things? Yes, building from the version in the Git repository would produce different results, if the sources in the repository do not correspond to the binary that is distributed in the Windows installer that I used to install Doxygen 1.8.13. To know if the repository fixes the issue, it is necessary to try reproducing the issue described in my original post. I will repeat those instructions here: To reproduce the crash in Doxygen 1.8.13, clone this repository: https://github.com/vinniefalco/Beast Then issue these commands from the root of the local directory: cd doc ./makeqbk.sh Can you please try this, to see if the defect has been resolved? I don't have the right environment set up to build Doxygen from sources. |
From: L A W. <do...@tl...> - 2017-04-26 00:35:25
|
Vinnie Falco wrote: > On Tue, Apr 25, 2017 at 11:57 AM, L A Walsh <do...@tl...> wrote: > >> ?? Beast? ?? >> For me it was a different project. >> >> From what I understand, different files are included in the >> git-version than come in the tarball. might >> that not change things? >> > > Yes, building from the version in the Git repository would produce > different results, if the sources in the repository do not correspond > to the binary that is distributed in the Windows installer that I used > to install Doxygen 1.8.13. > > To know if the repository fixes the issue, it is necessary to try > reproducing the issue described in my original post. I will repeat > those instructions here:... > Perhaps you will understand, but I'm more interested in how the project in bugzilla bug 781306 is affected. 1) if it was the same bug, and 2) if the fix works for for the project that that the bugzilla bug was filed against. > |
From: Vinnie F. <vin...@gm...> - 2017-04-26 00:52:45
|
On Tue, Apr 25, 2017 at 12:49 AM, L A Walsh <do...@tl...> wrote: > Dimitri van Heesch wrote: >> Hi Vinnie, >> >> Looks like the issue is already fixed in the latest version from Github. Is there a Windows installer for what's at the tip of the main GitHub repository branch? |