User forums > Help

CodeBlocks cash when "Find declaration " on some symbol

<< < (3/5) > >>

ollydbg:

--- Quote from: Loaden on February 22, 2011, 06:37:46 am ---The rev6306 likes for resoved this issue:

--- Code: ---#include <vector>

namespace CollaGEN
{
    using namespace std;
    namespace Engine
    {
        using namespace std;
        int aaa;
    }
}

int main()
{
    CollaGEN::Engine::vector<int> v;
    CollaGEN::vector<float> vf;
    return 0;
}

--- End code ---

--- End quote ---
Why?
I think rev 6303 has some problems.
I don't think adding "std" as "Engine" 's ancestor is a good idea, this will cause a lot of headache.

nanyu:
I have moved out all "using namespace ..." , but c::b crash yet. :(
waitting for your help..
now I install two c::b on my pc. :)

ollydbg:

--- Quote from: nanyu on February 23, 2011, 03:59:37 am ---I have moved out all "using namespace ..." , but c::b crash yet. :(
waitting for your help..
now I install two c::b on my pc. :)

--- End quote ---
I'm trying to find the real bug :D

ollydbg:
Here is the candidate patch to solve the crash bug.

The crash bug caused when ancestors are recursive.
e.g.:
there is a token class A, its ancestorsString can be "B;C;D"
and for a token class B, its ancestorsStirng could be "A;C;D"
you see, there is a hierarchy loop.

this is mostly caused by rev 6303, because a lot of un-related ancestors were added. I think we should use another method like (use a context variable to remember the current exposed namespace instead the way rev 6303's method)

my patch does not solve the bug in rev 6303.

my patch just avoid the endless loop and crash.

MortenMacFly:

--- Quote from: ollydbg on February 23, 2011, 08:52:38 am ---Here is the candidate patch to solve the crash bug.
[...]
my patch just avoid the endless loop and crash.

--- End quote ---
Mmmh... why don't you simply do a:

--- Code: ---    wxStringTokenizer tkz(token->m_AncestorsString, _T(","));
    token->m_AncestorsString.Clear();

--- End code ---
Instead of all this copying (not sure how wxStringTokenizer is implemented though... :oops:)? And what about the commented stuff? You change functionality here... was that on purpose (what about side-effects)?

Navigation

[0] Message Index

[#] Next page

[*] Previous page