From: Holger Kiehl <Holger.Kiehl@dwd.de>
To: Glynn Clements <glynn@gclements.plus.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Question about core files
Date: Fri, 9 Oct 2009 12:12:52 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0910091210220.12677@diagnostix.dwd.de> (raw)
In-Reply-To: <19149.12819.386168.598502@cerise.gclements.plus.com>
On Thu, 8 Oct 2009, Glynn Clements wrote:
>
> Holger Kiehl wrote:
>
>>>> Most the time I compile my application without the -g option due to
>>>> performance reasons.
>>>
>>> The -g switch has absolutely no effect upon performance. It simply
>>> causes and additional section to be added to the resulting binary.
>>> When the program is run normally (i.e. not under gdb), that section
>>> won't be mapped. The only downside to -g is that it increases the size
>>> of the file.
>>
>> But when executing the program will it not read the whole binary which
>> is much larger with debug information and so will take longer (just the
>> first reading of the binary)?
>
> No. Binaries aren't "read", they're mapped (with mmap); pages are read
> into memory on demand. The loader only maps the sections which are
> actually required, which doesn't include the debug sections.
>
Thanks for the clarification!
Holger
next prev parent reply other threads:[~2009-10-09 12:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 14:04 Question about core files Holger Kiehl
2009-10-06 14:41 ` Manish Katiyar
2009-10-07 13:28 ` Holger Kiehl
2009-10-07 13:54 ` Manish Katiyar
2009-10-07 14:21 ` Holger Kiehl
2009-10-07 17:36 ` Manish Katiyar
2009-10-08 18:47 ` Manish Katiyar
2009-10-09 12:09 ` Holger Kiehl
2009-10-09 12:15 ` Manish Katiyar
2009-10-09 12:43 ` Holger Kiehl
2009-10-10 8:35 ` Glynn Clements
2009-10-10 9:08 ` Manish Katiyar
2009-10-10 16:56 ` Holger Kiehl
2009-10-07 4:45 ` Glynn Clements
2009-10-07 13:43 ` Holger Kiehl
2009-10-08 0:28 ` Glynn Clements
2009-10-09 12:12 ` Holger Kiehl [this message]
2009-10-07 4:58 ` vinit dhatrak
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=Pine.LNX.4.64.0910091210220.12677@diagnostix.dwd.de \
--to=holger.kiehl@dwd.de \
--cc=glynn@gclements.plus.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).