User forums > Nightly builds

The 08 February 2014 build (9639) is out.

<< < (2/8) > >>

dmoore:
Ubuntu packages building here

damorin:
Hi,

something new in this release. Each time I try "Find functions calling <x>", CSCOPE crash.

I noticed the cscope database "cscope.out" have been renamed "ncscope.out".

Renaming it to the original name is fixing the problem.

I'm using cscope v15.7a

maryjeck:

--- Quote from: jens on February 09, 2014, 11:56:06 am ---
--- Quote from: maryjeck on February 09, 2014, 11:43:16 am ---There must be something wrong with it。

When I open an Project.
There are lost a word like like this "NativeParser::OnParserEnd(): Project '******' parsing stage done!".

and I can do nothing with it,it FC.

--- End quote ---
Where do you see this messages ?
Can you provide a sample (minimal) workspace/project where this occurs ?

--- End quote ---

build(9619):
The message is like this:
NativeParser::CreateParser(): Finish creating a new parser for project '***********'
NativeParser::OnParserEnd(): Project '********' parsing stage done!

build(9639):
like this:
NativeParser::CreateParser(): Finish creating a new parser for project '***********'

Only one word.

ollydbg:

--- Quote from: maryjeck on February 10, 2014, 03:46:16 am ---
--- Quote from: jens on February 09, 2014, 11:56:06 am ---
--- Quote from: maryjeck on February 09, 2014, 11:43:16 am ---There must be something wrong with it。

When I open an Project.
There are lost a word like like this "NativeParser::OnParserEnd(): Project '******' parsing stage done!".

and I can do nothing with it,it FC.

--- End quote ---
Where do you see this messages ?
Can you provide a sample (minimal) workspace/project where this occurs ?

--- End quote ---

build(9619):
The message is like this:
NativeParser::CreateParser(): Finish creating a new parser for project '***********'
NativeParser::OnParserEnd(): Project '********' parsing stage done!

build(9639):
like this:
NativeParser::CreateParser(): Finish creating a new parser for project '***********'

Only one word.

--- End quote ---
Ok, so it looks like the CC's parser hangs or go to some infinite loop.
If you see the change between rev 9619 and 9639, there are few CC related changed.


--- Code: ---Revision: 9639
Author: ollydbg
Date: 2014-2-8 17:33:14
Message:
- CC: use wx_str() instead of c_str().
-------------------------------
M(T ) : /trunk/src/plugins/codecompletion/nativeparser.cpp

Revision: 9638
Author: ollydbg
Date: 2014-2-8 17:32:33
Message:
* CC: fix a bug (logic error) introduced in rev 9601.
-------------------------------
M(T ) : /trunk/src/plugins/codecompletion/parser/tokenizer.cpp


Revision: 9636
Author: fuscated
Date: 2014-2-4 7:15:50
Message:
- CC: Make the code a bit more readable
-------------------------------
M(T ) : /trunk/src/plugins/codecompletion/parser/parserthread.cpp

Revision: 9635
Author: fuscated
Date: 2014-2-4 7:15:45
Message:
- wx30: Fix a format specifier mismatch assert
-------------------------------
M(T ) : /trunk/src/plugins/codecompletion/parser/parserthread.cpp


--- End code ---

I guess the change of rev9638 (* CC: fix a bug (logic error) introduced in rev 9601.) cause this bug. But in-fact rev 9638 is going fix a logic error, so another guess is that rev 9601 does not truly fix the bug.

I would welcome a test project/workspace. Meanwhile, I will re-test the sample project in this discussion:  NativeParser lockup when parsing Visual Studio 2013 and Boost 1.55.0 headers later today.

EDIT: Code blocks using too much cpu, this contains a sample project which will lead to hang issue.

ollydbg:

--- Quote from: ollydbg on February 10, 2014, 04:35:08 am ---...
I would welcome a test project/workspace. Meanwhile, I will re-test the sample project in this discussion:  NativeParser lockup when parsing Visual Studio 2013 and Boost 1.55.0 headers later today.

EDIT: Code blocks using too much cpu, this contains a sample project which will lead to hang issue.

--- End quote ---
FYI: I test the sample project in above link with C::B rev 9643, I can't find see the hang issue here. So, I definitely need a reproducer, thanks.

Navigation

[0] Message Index

[#] Next page

[*] Previous page