You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are using a *nix platform, you should be able to get a stacktrace using gdb. This helps us compare stacktraces so that we can figure out what caused the crash, and how to best fix it.
How to do this on windows? The link you provided does not tell
(If you look in the OS field you will see I am running this on windows)
Has anyone tested my exsample?
On 2013-04-18 17:11:16 +0000, Kevin McBride wrote:
Created attachment 241839
Testcase
I was able to reproduce this bug using the attached example on Windows. According to the stacktrace, doxygen appears to crash somewhere within the Windows libraries. In order for me to produce a stacktrace, I will have to find a way to get doxygen to compile on Visual Studio.net 2010 (which is my current debugger).
I have a separate bug report filed regarding the conversion of the Visual Studio files in the source code of doxygen to VS.net 2010 SP1.
On 2013-04-18 17:19:12 +0000, Kevin McBride wrote:
Doxygen developers, on Windows, the bug appears to crash when generating search indices. Below is the output from the console:
Searching for include files...
Searching for example files...
Searching for images...
Searching for dot files...
Searching for msc files...
Searching for files to exclude
Searching for files to process...
Searching for files in directory C:/Users/Kevin/Documents/Doxygen/Bug 694685
Reading and parsing tag files
Preprocessing C:/Users/Kevin/Documents/Doxygen/Bug 694685/a.c...
Parsing file C:/Users/Kevin/Documents/Doxygen/Bug 694685/a.c...
Preprocessing C:/Users/Kevin/Documents/Doxygen/Bug 694685/b.c...
Parsing file C:/Users/Kevin/Documents/Doxygen/Bug 694685/b.c...
Building group list...
Building directory list...
Building namespace list...
Building file list...
Building class list...
Associating documentation with classes...
Computing nesting relations for classes...
Building example list...
Searching for enumerations...
Searching for documented typedefs...
Searching for members imported via using declarations...
Searching for included using directives...
Searching for documented variables...
Building member list...
Searching for friends...
Searching for documented defines...
Computing class inheritance relations...
Computing class usage relations...
Flushing cached template relations that have become invalid...
Creating members for template instances...
Computing class relations...
Add enum values to enums...
Searching for member function documentation...
Building page list...
Search for main page...
Computing page relations...
Determining the scope of groups...
Sorting lists...
Freeing entry tree
Determining which enums are documented
Computing member relations...
Building full member lists recursively...
Adding members to member groups.
Computing member references...
Inheriting documentation...
Generating disk names...
Adding source references...
Adding xrefitems...
Sorting member lists...
Computing dependencies between directories...
Generating citations page...
Counting data structures...
Resolving user defined references...
Finding anchors and sections in the documentation...
Combining using relations...
Adding members to index pages...
Generating style sheet...
Generating search indices...
On 2013-04-18 17:47:22 +0000, Kevin McBride wrote:
Correction on stacktraces: because I have not yet been able to compile doxygen with debugging symbols, I do not have a decent stacktrace to put on this bug report.
On 2013-05-11 17:30:14 +0000, Dimitri van Heesch wrote:
Confirmed. Should be fixed in the next subversion update.
On 2013-05-19 12:36:14 +0000, Dimitri van Heesch wrote:
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. 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.
The text was updated successfully, but these errors were encountered:
status RESOLVED severity critical in component build for ---
Reported in version 1.8.3.1 on platform Other
Assigned to: Dimitri van Heesch
Original attachment names and IDs:
On 2013-02-25 15:47:04 +0000, mah@danfoss.com wrote:
On 2013-02-25 23:01:55 +0000, Kevin McBride wrote:
On 2013-04-18 15:07:17 +0000, mah@danfoss.com wrote:
On 2013-04-18 17:11:16 +0000, Kevin McBride wrote:
On 2013-04-18 17:19:12 +0000, Kevin McBride wrote:
On 2013-04-18 17:47:22 +0000, Kevin McBride wrote:
On 2013-05-11 17:30:14 +0000, Dimitri van Heesch wrote:
On 2013-05-19 12:36:14 +0000, Dimitri van Heesch wrote:
The text was updated successfully, but these errors were encountered: