-
I have rebuilt KScope-1.9.4 using qt-4.4.0 (before I used qt-4.5.1) and the « Query » menu got active.
2009-07-02 10:54:58 UTC in KScope
-
Well, it is not a QT version related issue.
I could resolve the issue by modifying default cscope path in "cscope.cpp" to seek local cscope location. Using just "configure engine" menu did not work.
Now the projects are built (database and other files generated) but "Query" tabs are inactive (except from "Call tree" that runs perfectly).
2009-07-02 10:37:26 UTC in KScope
-
I will try with qt-4.4.0 version as it seems to be the one used to disign KScope-1.9.x.
2009-07-01 13:27:29 UTC in KScope
-
Hi All;
It’s great that kscope does not need kde any more, thank you for this evolution.
I have built Kscope-1.9.4 (using Qt-4.5) on i686-linux2.6 and sparc-solaris2.10 without any problem. I also set cscope and ctags engines paths.
On both architectures, when creating a new project, the “Building project” box appears but stays at “initializing” step. Then, the program exits...
2009-06-29 11:15:06 UTC in KScope
-
Hi,
I have investigated about our C code, and there may be like:
//#########################################################
They are used to separate or make visible parts of code. When they are not ended by a double slash ‘//’ this activate the bug.
Such lines are used also to frame the license header in sources files.
Thanks.
2009-03-31 13:55:00 UTC in cscope
-
Many thanks for your answer.
Fist I had observed the issue on perl code projects. But we had also a ticket from a user working on a C++ project. As C projects are extra larges, and this issue seemed to happen randomly, I preferred first to investigate using perl code where the issue was almost assured.
I made tests using a unique file project (see previous posts), and launched cscope-15.6 like...
2009-03-30 15:03:30 UTC in cscope
-
Hi again
I have investigated about the reason of this line number offset.
It seems that when Cscope encounters the character sequence: "#" , The line index is reduced by one.
In examples below we are searching for SymLink reference
______________________________
#
#
sub SymLink {
my ( $from, $to ) = @_;
print "Linking $to -> $from\n";
symlink $from, $to;
}
====>...
2009-03-27 15:44:41 UTC in cscope
-
Hi again
I have investigated about the reason of this line number offset.
It seems that when Cscope encounters the character sequence: "#<EOL>" , The line index is reduced by one.
In examples below we are searching for SymLink reference
______________________________
#
#
sub SymLink {
my ( $from, $to ) = @_;
print "Linking $to -> $from\n";...
2009-03-27 15:41:20 UTC in KScope
-
Hi again
I have investigated about the reason of this line number offset.
It seems that when Cscope encounters the character sequence: "#" , The line index is reduced by one.
In examples below we are searching for SymLink reference
______________________________
#
#
sub SymLink {
my ( $from, $to ) = @_;
print "Linking $to -> $from\n";
symlink $from, $to;
}
====>...
2009-03-27 15:40:40 UTC in cscope
-
Hi everybody
While browsing perl code (for example "apvsys" which is a sourceforge project) using Cscope, line numbers indicated in the cscope output does not match line numbers in the editor.
For perl it is systematic, but this can happen also while browsing C++ code.
Has any body already encountered this issue and has it already been solved.
Regards
Farouk.
2009-03-27 11:23:21 UTC in cscope
