New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault in scanner.l, "// copy special list items" (Origin: bugzilla #588968) #3450

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity critical in component general for ---
Reported in version unspecified on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2009-07-18 17:23:37 +0000, Axel Kollmorgen wrote:

the attached files cause doxygen to stop with a segfault. the error happens in this part of scanner.l:

if (current->sli) // copy special list items
{
QListIterator li(*current->sli);
ListItemInfo *lii;
for (li.toFirst();(lii=li.current());++li)
{
previous->addSpecialListItem(lii->type,lii->itemId); // <<<< HERE
}
delete current->sli;
current->sli = 0;
}

problem: 'previous' is undefined (in the special case of these files).

quickfix:

  •   if (current->sli) // copy special list items
    
  •   if (current->sli && previous) // copy special list items
    

proper fix: no idea, because i'm not so familiar with doxygen, the scanner, etc. one hint that this needs some more work is the section just above this code, which is '#if 0' outcommented. would be nice if someone with more insight could look over this.

On 2009-07-18 17:25:35 +0000, Axel Kollmorgen wrote:

Created attachment 138685
action.php from xmlrpc-2.2 exposing the bug

On 2009-07-18 17:27:43 +0000, Axel Kollmorgen wrote:

Created attachment 138687
common.php from xmlrpc-2.2 exposing the bug

On 2009-07-19 07:45:18 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2009-07-21 00:43:34 +0000, Axel Kollmorgen wrote:

will you just add the " && previous", or change something in the general processing?

On 2009-08-20 10:13:22 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.0. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment