This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Go To Definition is a game of luck

Hello,

the usage of the "Go To Definition" function is one of the most important function of the IDE for me. Working with software I`m using this function hundreds of times per day. In the past (up to 5.24.2) this was working without any problems. Today (5.35.0) I have have so much problems with this function. In 50% of all cases it works fine as usual. In the other 50% I`m always getting this enervating "No browse info for symbol in this context".
- yes, I enabled the creation of the browse information in the options
- yes, I rebuild the complete code
- yes, the header file with the searched information is included (open document and ctrl-f-search will find)
- yes, I hoped that with 5.35 the problem would be silently fixed ... but it does not
I can not imagine that such a great IDE like uvision has so elementary bugs ... the mistake must be on my side. Where is my fault ?
Please help !

friendly regards
Recently

Parents
  • I run this tool

    github.com/.../cloc

    on my project and got  >100k line of code.

    No idea how this would be described as in relation to what uVision is designed to handle. Big/middle/small sized project ?

    a source code module or at least a code snippet is necessary for Arm to reproduce the issue

    Is not there some log where the browse info generator outputs its state and reason of failure ? If not, could you add this to next release ?

    Arm compiler v6.x, the browse info is generated in the background of µVision dynamically

    It is confusing because my program links so all neccesary information is clearly available to the linker (this is how v5 works as you explained). But with v6 browse info must be extracted without linking. Interesting.

Reply
  • I run this tool

    github.com/.../cloc

    on my project and got  >100k line of code.

    No idea how this would be described as in relation to what uVision is designed to handle. Big/middle/small sized project ?

    a source code module or at least a code snippet is necessary for Arm to reproduce the issue

    Is not there some log where the browse info generator outputs its state and reason of failure ? If not, could you add this to next release ?

    Arm compiler v6.x, the browse info is generated in the background of µVision dynamically

    It is confusing because my program links so all neccesary information is clearly available to the linker (this is how v5 works as you explained). But with v6 browse info must be extracted without linking. Interesting.

Children
No data