everyone. I'm reading the Wireshark source code these days. After importing all wireshark sources into Source Insight 3.50.0072, I found that several .c files can't be parsed correctly. The left "Symbol Window" can't display the local symbols, with a error shows "Parse Too complex in Packet.c(epan)". The file size is not the cause, because many bigger files can be parsed correctly. Also I am using the Git tool to download the Wireshark source trunk and have sucessfully compiled it, so the code is ok. I have tried several versions of Source Insight. Unfortunately they share the same problem.
The web page of the epan/packet.c source code is: packet.c
The Tsharp.c file has the same problem with the symbol window. So I doubt if this is a bug of Source Insight? How to solve this? Thx.
Some other source code processing tools, with names such as "GCC", "Clang", "Microsoft Visual Studio", "Oracle Studio", "HP aCC", etc., don't seem to have a problem with that file, so I rather strongly believe that this is a deficiency of Source Insight, even if it's not technically a "bug" (perhaps they just have some hardwired limit in the program, so that it's "by design").
And given the number of "Fix: C/C++ ... parsing ..." items in their change notes, I wouldn't be at all surprised to find that it's Yet Another Bug.
How to solve this? File a bug with Source Dynamics and tell them you won't buy any more licenses until they fix it, and use some other tool in the interim.