Open lansfy opened 11 years ago
Can you post the full stack trace? A NullPointException usually means there is a bug in the code.
I do agree that both the c and java versions of this command could use a max depth (I've triggered an OutOfMemoryError playing with the java call hierarchy command in one place), but without seeing what is causing the NullPointerException for you, I'm not sure that adding a max depth would solve your issue.
Thank you for response.
Full error stack (with some view optimization, as it is 1027 lines long)
java.lang.NullPointerException
at org.eclim.plugin.cdt.command.hierarchy.CallHierarchyCommand$Call.<init>(CallHierarchyCommand.java:346)
at org.eclim.plugin.cdt.command.hierarchy.CallHierarchyCommand.findCallers(CallHierarchyCommand.java:235)
at org.eclim.plugin.cdt.command.hierarchy.CallHierarchyCommand.findCallers(CallHierarchyCommand.java:204)
at org.eclim.plugin.cdt.command.hierarchy.CallHierarchyCommand.formatElement(CallHierarchyCommand.java:324)
-- next fragment repeated 339 times
at org.eclim.plugin.cdt.command.hierarchy.CallHierarchyCommand.findCallers(CallHierarchyCommand.java:244)
at org.eclim.plugin.cdt.command.hierarchy.CallHierarchyCommand.findCallers(CallHierarchyCommand.java:182)
at org.eclim.plugin.cdt.command.hierarchy.CallHierarchyCommand.formatElement(CallHierarchyCommand.java:324)
---
I use eclim as AST-server for examine source of our project. Project is big, so then I try run command
I got next error
because call hierarhy is too big, I think. Can you add special parameter max_depth to c_callhierarchy command to restrict size of call hierarchy tree?