Bug 281156

Summary: can't "jump to definition" in external C file
Product: [Applications] kdevelop Reporter: Aleks <abirvalg>
Component: Language Support: CPP (old)Assignee: kdevelop-bugs-null
Status: RESOLVED WORKSFORME    
Severity: normal CC: aleixpol
Priority: NOR    
Version First Reported In: 4.2.3   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Aleks 2011-09-01 09:09:56 UTC 
Version:           4.2.3
OS:                Linux

If function is declared extern, "jump to definition" doesnt jump to the actual definition but to extern declaration.

Reproducible: Always

Steps to Reproduce:

I have a 1.c file which defines a foo()
Then there is another 2.c file which declares extern foo() and later on uses foo()
When I highlight foo() in 2.c and choose "Jump to definition", it jumps to extern foo() in 2.c, which is declaration and not definition.
When I highlight foo() in 2.c and hover cursor, I get a popup window where I select "Show uses", then in the next window Definition is shown correctly to be in 1.c, which evidences that KDevelop is aware of the correct place of foo()'s definition


Expected Results:  
jump to definition
Comment 1 Aleks 2011-09-02 08:44:19 UTC 
Update:
When forward declaration of foo() in 1.c was made, behaviour became as expected.
This is probably a deficiency of code parsing engine.
Comment 2 Andrew Crouthamel 2018-11-11 04:25:11 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-21 04:30:55 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2023-01-08 22:44:44 UTC 
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-01-23 05:04:25 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-02-07 03:55:03 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!