bug in rev 6045 of handling typedef statement

[ollydbg]

hi, these codes( see below ) in ParserThread.cpp in HandleTypedef function

Code Select Expand


        else if (token == _T("*"))
        {
            m_IsPointer = false;
            continue;
        }
        else if (peek == ParserConsts::comma)
        {
            m_Tokenizer.UngetToken();
            if (components.size() != 0)
            {
                wxString ancestor;
                while (components.size() > 0)
                {
                    wxString token = components.front();
                    components.pop();

                    if (!ancestor.IsEmpty())
                        ancestor << _T(' ');
                    ancestor << token;
                    ReadClsNames(ancestor);
                }
            }
        }


were newly added in the rev 6046 to handle something like

Code Select Expand


typedef struct localeinfo_struct
{
    pthreadlocinfo locinfo;
    pthreadmbcinfo mbcinfo;
} _locale_tstruct, *_locale_t;


But it seems there are some bugs, I'd like someone can help me to solve this bug. Thanks.
If we can't solve this bug, I need to "remove" these code snippet.

[blueshake]

hi,ollydbg

you need to move the codes:

Code Select Expand

                    ReadClsNames(ancestor);

out of the while statement.

by the way.are you in gtalk?

[ollydbg]

There's still some thing wrong cc.
rev 6091.
Open the contribute plugin workspace, and active threadsearch plugin.
Then open the "src\plugins\contrib\ThreadSearch\ThreadSearch.h", then you can see there's no class shown in "symbols browser".

Edit：
I just test in an old version(rev 5908), and found that this bug was there too. so, it is an old bug, not introduced recently.

[Loaden]

There's still some thing wrong cc.
rev 6091.
Open the contribute plugin workspace, and active threadsearch plugin.
Then open the "src\plugins\contrib\ThreadSearch\ThreadSearch.h", then you can see there's no class shown in "symbols browser".

Edit：
I just test in an old version(rev 5908), and found that this bug was there too. so, it is an old bug, not introduced recently.

work here, svn 6091.

[ollydbg]

I just test it and it works now in rev 6091.