From: Shriramana Sharma <samjnaa@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: How did KDbg find out the source corresponding to my executable?
Date: Fri, 27 Apr 2007 20:36:20 +0530 [thread overview]
Message-ID: <4632116C.70109@gmail.com> (raw)
Has someone here used KDbg?
Just a few minutes ago, I tried KDbg, the KDE front-end to gdb. (The
change in position of g between the two names amuses me for some reason.)
When I selected an executable which was located at a location different
from its source, KDbg automatically found out the location of the
source-file and opened it for setting breakpoints etc.
Is the path to the source embedded in every executable? Upon examining
the executable by nm for symbols I did not find the source path, but
maybe that is not a symbol. Okay: readelf has an entry corresponding to
the source filename but not the source path. Does KDbg search the home
directory for the source filename?
If not, how could KDbg correctly open the source file?
Shriramana Sharma.
P.S: I realize this is slightly OT since it asks a question about a KDE
application albeit most related to programming. I'm taking the chance
that someone here has used KDbg.
next reply other threads:[~2007-04-27 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 15:06 Shriramana Sharma [this message]
2007-05-04 13:34 ` How did KDbg find out the source corresponding to my executable? Glynn Clements
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=4632116C.70109@gmail.com \
--to=samjnaa@gmail.com \
--cc=linux-c-programming@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).