From: "John (Eljay) Love-Jensen" <eljay@adobe.com>
To: lehe <timlee126@yahoo.com>, GCC-help <gcc-help@gcc.gnu.org>
Subject: Re: difference between -g, -ggdb and -ggdb3
Date: Wed, 18 Feb 2009 16:44:00 -0000 [thread overview]
Message-ID: <C5C196E0.38449%eljay@adobe.com> (raw)
In-Reply-To: <22082494.post@talk.nabble.com>
Hi lehe,
> I was wondering what the difference between -g, -ggdb and -ggdb3 as option for
gcc?
-g produces debugging information in the OS¹s native format (stabs, COFF,
XCOFF, or DWARF 2).
-ggdb produces debugging information specifically intended for gdb.
-ggdb3 produces extra debugging information, for example: including macro
definitions. -ggdb by itself without specifying the level defaults to
-ggdb2 (i.e., gdb for level 2).
It is *possible* (I've heard) that the -ggdb can produce debugging
information that can confuse other debuggers if you are not using gdb. I
only use gdb, so I cannot confirm or refute that rumor.
So...
If you use gdb, use -ggdb (same as -ggdb2), or -ggdb1 (to help reduce the
debug footprint), or -ggdb3 (for additional debugging info).
If you do not use gdb...
Use -g and keep in mind that gdb works with the OS's native format too.
I use -g even though I use gdb exclusively when I use gcc/g++. I could use
-ggdb ... but I forget to type those extra three characters.
HTH,
--Eljay
next prev parent reply other threads:[~2009-02-18 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 16:28 lehe
2009-02-18 16:44 ` John (Eljay) Love-Jensen [this message]
2009-02-18 16:44 ` Diego Novillo
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=C5C196E0.38449%eljay@adobe.com \
--to=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=timlee126@yahoo.com \
/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).