Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign

Is CC crash, or Debugger plugin?

<< < (5/23) > >>

ollydbg:

--- Quote from: Loaden on July 09, 2011, 10:56:08 am ---
--- Quote from: oBFusCATed on July 08, 2011, 03:19:13 pm ---I guess there is some memory corruption happening somewhere, because a bug in std::set is highly unlikely.
Loaden any thoughts or ideas?

--- End quote ---
Please try rev7281.


--- End quote ---
@loaden:

the latest debugger branch rev 7276 and the trunk 7281 is nearly the same.

Loaden:

--- Quote from: ollydbg on July 09, 2011, 09:24:50 am ---@loaden:
I just look at the crash call stack OBF posted, I found that

Do we need to do the "parser“ and "TokensTree" locking when we are calling function ParseBuffer()?

It seems that I can't find any lockers in the call function chain. so, it seems the shared resource was not protected. :D

PS: As OBF's crash call stack was in debugger branch, so I only review cc's code in this branch. (not trunk).

--- End quote ---

--- Code: ---size_t NativeParser::MarkItemsByAI(ccSearchData* searchData, TokenIdxSet& result, bool reallyUseAI, bool isPrefix,
                                   bool caseSensitive, int caretPos)
{
    wxCriticalSectionLocker locker(s_TokensTreeCritical);
    result.clear();
--- End code ---
The locker added here.

ollydbg:

--- Quote from: Loaden on July 09, 2011, 11:49:28 am ---
--- Code: ---size_t NativeParser::MarkItemsByAI(ccSearchData* searchData, TokenIdxSet& result, bool reallyUseAI, bool isPrefix,
                                   bool caseSensitive, int caretPos)
{
    wxCriticalSectionLocker locker(s_TokensTreeCritical);
    result.clear();
--- End code ---
The locker added here.

--- End quote ---
Oh, that's my mistake... the crash reason is still unknown...

oBFusCATed:
Does the parser test project work on linux?
For me it crashes badly on strange places :(

ollydbg:

--- Quote from: oBFusCATed on July 10, 2011, 10:56:41 am ---Does the parser test project work on linux?
For me it crashes badly on strange places :(


--- End quote ---
So, you use the "parsertest-unix.cbp", that file is exacted to work. but mostly I'm using the "parsertest.cbp" under Windows.

what's the crash traceback?

Maybe, you can ask Loaden to test the linux parser test project.

Navigation

[0] Message Index

[#] Next page

[*] Previous page