SourceNavigator 4.5.1 : Parsing a given header file hangs cbrowser

SourceNavigator 4.5.1 : Parsing a given header file hangs cbrowser

[Joe Van Andel]

First, thanks for releasing such a nice product as Open Source.  I
really appreciate your efforts.

I build 4.5.1 on Redhat 6.2 (Pentium).

When I create a new project that contains the following header file

FilterParams.h
----------------------

class {
 public:
    FilterParams(float *
    int numParams;
    float *params;
    
} FilterParams, *FilterParamsPtr;
----------------------------

cbrowser hangs forever.

Note there is a syntax error in this header file - a missing parenthesis
on the ctor declaration. 
Once I fixed this bug, cbrowser runs as expected.

However, it would be nice if cbrowser had a more resilient error
recovery strategy :-)

Thanks again!


-- 
Joe VanAndel  	          
National Center for Atmospheric Research
http://www.atd.ucar.edu/~vanandel/
Internet: vanandel@ucar.edu
begin:vcard 
n:VanAndel;Joe
tel;fax:303-497-2044
tel;work:303-497-2071
x-mozilla-html:FALSE
url: http://www.atd.ucar.edu/~vanandel
org:National Center for Atmospheric Research;Remote Sensing Facility
adr:;;P.O. Box 3000;Boulder;CO;80307-3000;
version:2.1
email;internet:vanandel@ucar.edu
x-mozilla-cpt:;0
fn:Joe VanAndel
end:vcard

Re: SourceNavigator 4.5.1 : Parsing a given header file hangs cbrowser

[Gilles J. Seguin]

Joe Van Andel wrote:
> 
> First, thanks for releasing such a nice product as Open Source.  I
> really appreciate your efforts.
> 
> I build 4.5.1 on Redhat 6.2 (Pentium).
> 
> When I create a new project that contains the following header file
> 
> FilterParams.h
> ----------------------
> 
> class {
>  public:
>     FilterParams(float *
>     int numParams;
>     float *params;
> 
> } FilterParams, *FilterParamsPtr;
> ----------------------------
> 
> cbrowser hangs forever.

We certainely do not want that.

> Note there is a syntax error in this header file - a missing
> parenthesis on the ctor declaration.
> Once I fixed this bug, cbrowser runs as expected.
> 
> However, it would be nice if cbrowser had a more resilient error
> recovery strategy :-)

Must we provide a dialog asking for conformance to strict C++,
to different level of the standard.  And at he lowest level let
it be a fuzzy C parser.

I am very tempted to allow, get information from *.o file if
they are available, and even more if the object file was
compile with the debug information turn on.
Ask where library/executable genereted by this project are if any.

Re: SourceNavigator 4.5.1 : Parsing a given header file hangs cbrowser

[Ben Elliston]

   I am very tempted to allow, get information from *.o file if they are
   available, and even more if the object file was compile with the debug
   information turn on. Ask where library/executable genereted by this
   project are if any.

I had actually thought about writing an object file parser using the BFD
library.  This could be used to discover the relationships between symbols
in object files.  It could be useful to someone trying to improve the
performance of their application by tweaking the linking order of object
files.

Also great if you don't have the source code to programs you're trying to
debug. ;-)

Ben

Re: SourceNavigator 4.5.1 : Parsing a given header file hangs cbrowser

[Gilles J. Seguin]

Ben Elliston wrote:
> 
>    I am very tempted to allow, get information from *.o file if they are
>    available, and even more if the object file was compile with the debug
>    information turn on. Ask where library/executable genereted by this
>    project are if any.
> 
> I had actually thought about writing an object file parser using the BFD
> library.  This could be used to discover the relationships between symbols
> in object files.  It could be useful to someone trying to improve the
> performance of their application by tweaking the linking order of object
> files.

My first thought was to used it as a tool to validate the parser.

Other things that I am looking for, is the area of sequence
diagrams and state diagrams. Can we discover callback sequences
and declarations.

Re: SourceNavigator 4.5.1 : Parsing a given header file hangs cbrowser

[Ben Elliston]

   Other things that I am looking for, is the area of sequence diagrams
   and state diagrams. Can we discover callback sequences and
   declarations.

To a certain extent, that's very hard.  While it is possible to trace
callbacks through assignment to pointers-to-functions:

	callb = funcA;

It's harder when the callback is assigned at runtine:

	switch (rand() % 3)
	{
	  case 0:
	    callb = funcA;
	  case 1:
	    callb = funcB;	
	  case 2:
	    callb = funcC;
	};

Or worse, involving pointer arithmetic!

	callb = log + 0x100;

(Yes, eww).

Ben