Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Lennyk <lennyk430@gmail.com>
To: gdb@sourceware.org
Subject: Core dump information when code is optimized
Date: Thu, 16 Apr 2009 07:00:00 -0000	[thread overview]
Message-ID: <49E6D676.9000108@gmail.com> (raw)

Hi,

When I compile only with -O1 flag - my core dump information does not 
show line number or offset (when a segmentation fault has occurred).
Only when I add the -g flag does the core dump contain line number 
information - but the executable's size grows significantly!

Is there a way to get this information with core dump - but maintain the 
optimized sized executable?

Thanks!


             reply	other threads:[~2009-04-16  7:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16  7:00 Lennyk [this message]
2009-04-16  9:00 ` Joel Brobecker
2009-04-17  7:59 ` Michael Snyder
2009-04-20 14:47   ` Lennyk

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=49E6D676.9000108@gmail.com \
    --to=lennyk430@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