From: Fizzo <fizzo1973@gmail.com>
To: gdb@sourceware.org
Subject: Problem with ddd and source file visibility
Date: Tue, 04 Aug 2009 07:27:00 -0000 [thread overview]
Message-ID: <24803540.post@talk.nabble.com> (raw)
Hello,
I am having a problem using ddd: I cant seem to fix the source file
visibility in ddd.
here is the situation...
I have a project made up of the following components:
- library A in its own directory where source files are split in src and inc
directories
- library B in its own directory where source files are split in src and inc
directories
- the program itself in its own directory where source files are split in in
src and inc directories.
When I debug the executable file I can correctly see the main file (which is
part of the program) and it can debugged fine, until I try to step into a
function listed in library A.
If I open the "Open Source" Dialog, I can see the files being part of the
program, then I can see some header files of library A, but I cant see any
of the source files of library A.
I tried to add the directory both using the gdb 'directory' command from gdb
prompt, and the 'GDB Settings' dialog box of DDD; nevertheless source files
for library A are nowhere to be seen :(
If I try to list a function defined in library A using 'list <FunctionName>'
here is the result:
No line number information available for address 0x.....
As far as I know both executables and libraries have been compiled using the
-ggdb option.
Is there anybody who could give me some hints on how to detect the problem?
If you need additional feel free to ask.
thanks in advance
Have a Nice Day
--
View this message in context: http://www.nabble.com/Problem-with-ddd-and-source-file-visibility-tp24803540p24803540.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
next reply other threads:[~2009-08-04 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 7:27 Fizzo [this message]
2009-08-04 8:03 ` Fizzo
2009-08-08 7:04 ` Baurzhan Ismagulov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24803540.post@talk.nabble.com \
--to=fizzo1973@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox