Bug 114430 - Steping into a library function does not open the file. [NEEDINFO]
Summary: Steping into a library function does not open the file.
Status: NEW
Alias: None
Product: Red Hat Developer Suite
Classification: Retired
Component: CDT (Show other bugs)
(Show other bugs)
Version: 1.0
Hardware: i686 Linux
Target Milestone: ---
Assignee: eclipse-bugs
QA Contact: eclipse-bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-28 01:02 UTC by Chandrakala Chavva
Modified: 2008-08-02 23:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
bugzilla: needinfo?

Attachments (Terms of Use)

Description Chandrakala Chavva 2004-01-28 01:02:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922

Description of problem:
When a Step into command is issued on a library function (like printf)
should open the file printf.c At present the debugger knows the
location of the file but it is asking us to do it manually.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.See above

Additional info:

Comment 1 Keith Seitz 2004-08-03 22:02:28 UTC
I'm not quite sure what you mean when you say "At present the debugger
knows the location of the file but is asking us to do it manually."

Does that mean that the debug UI has stepped into printf but cannot
display the source file? Or does it step OVER the function call?

There is one way to check what is happening: run command-line gdb on
your executable. Just load it ("file myexe"), and then ask for info
about printf ("info func printf").

If gdb says something like "non-debugging symbols: printf", then gdb
did NOT find debug information for printf, and when asked to step into
it, it will actually step OVER it.

However, if it returns something else (like a filename), then try
"list printf".

If gdb lists the function, then we're definitely looking at a CDT
debugger UI bug.

If gdb cannot list the file, then it is possible that the debug info
is "wrong". I don't know whether we taught gdb to know about the
debuginfo rpms and the like, though.
It is more likely that the file doesn't exist where gdb thinks it is
supposed to. Again, the output of "info func printf" should tell you
where gdb thinks the file is. Try inspecting the EXACT path mentioned
by gdb in the filesystem.

Note You need to log in before you can comment on or make changes to this bug.