From: vadiraj <vadis.list@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: How to create separate files with debug information?
Date: Mon, 16 Apr 2007 10:42:46 +0530 [thread overview]
Message-ID: <1176700366.9368.3.camel@blr-img.blr.novell.com> (raw)
In-Reply-To: <4622F702.6000301@gmail.com>
On Mon, 2007-04-16 at 09:39 +0530, Shriramana Sharma wrote:
> Now the questions:
>
> First: Is this kind of providing separate debug files applicable only
> for library or also for applications?
Yes you can have debug file for applications too.
>
> Second: How do I create such .debug files with debug information only? I
> find that these debug files are not executables.
any binary/library compiled with debug flag are with debugging
information. I believe .debug in your example will be linked to the file
that the application will link. Ex. libQtGui.so ->
libQtGui.so.4.2.3.debug
Cheers,
Vadi
next prev parent reply other threads:[~2007-04-16 5:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 4:09 How to create separate files with debug information? Shriramana Sharma
2007-04-16 5:12 ` vadiraj [this message]
2007-04-16 13:49 ` 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=1176700366.9368.3.camel@blr-img.blr.novell.com \
--to=vadis.list@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).