public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Alfred M. Szmidt" <ams@gnu.org>
To: John Carter <john.carter@tait.co.nz>
Cc: gcc-help@gcc.gnu.org
Subject: Re: -g vs -g3 -ggdb3
Date: Thu, 24 May 2007 16:18:00 -0000	[thread overview]
Message-ID: <E1HrFtl-0001lv-Ke@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0705240952220.984@parore.tait.co.nz> (message from 	John Carter on Thu, 24 May 2007 09:58:12 +1200 (NZST))

   Q1 Which is the best setting to use with gdb (under linux)?

It depends on the task.

   Q2 Is there anyway to decrease the bloat?

You can always use a lower debugging level, but then you lose some
information.  It is always possible to debug programs just by
examining the assembler output as well.

   Q3 Do we need to say -g3 -ggdb3 or is -ggdb3 sufficient?

-ggdb produces debuging information only usable by gdb, while -g
produces whatever the native system uses.

      reply	other threads:[~2007-05-24 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 22:00 John Carter
2007-05-24 16:18 ` Alfred M. Szmidt [this message]

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=E1HrFtl-0001lv-Ke@localhost \
    --to=ams@gnu.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=john.carter@tait.co.nz \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).