public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug driver/94491] New: -g2 debugging level is not documented
@ 2020-04-05 11:04 slyfox at inbox dot ru
  2020-04-06  6:49 ` [Bug driver/94491] " marxin at gcc dot gnu.org
  0 siblings, 1 reply; 2+ messages in thread
From: slyfox at inbox dot ru @ 2020-04-05 11:04 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94491

            Bug ID: 94491
           Summary: -g2 debugging level is not documented
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: slyfox at inbox dot ru
  Target Milestone: ---

A tiny backstory: to profile a program I built it with '-g'. The result did not
fit in my RAM and machine crashed. Looking at the doc I found out '-g' means
'-g2' (and not '-g1').

Worth documenting what -g2 actually do? Others are interested as well:
https://stackoverflow.com/questions/10475040/gcc-g-vs-g3-gdb-flag-what-is-the-difference


'man gcc' covers only 0,1 and 3:

"""
       -glevel
       -ggdblevel
       -gstabslevel
       -gxcofflevel
       -gvmslevel
           Request debugging information and also use level to specify how much
information.  The default level is 2.

           Level 0 produces no debug information at all.  Thus, -g0 negates -g.

           Level 1 produces minimal information, enough for making backtraces
in parts of the program that you don't plan to debug.  This includes
descriptions of functions and external
           variables, and line number tables, but no information about local
variables.

           Level 3 includes extra information, such as all the macro
definitions present in the program.  Some debuggers support macro expansion
when you use -g3.

           If you use multiple -g options, with or without level numbers, the
last such option is the one that is effective.

           -gdwarf does not accept a concatenated debug level, to avoid
confusion with -gdwarf-level.  Instead use an additional -glevel option to
change the debug level for DWARF.
"""

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug driver/94491] -g2 debugging level is not documented
  2020-04-05 11:04 [Bug driver/94491] New: -g2 debugging level is not documented slyfox at inbox dot ru
@ 2020-04-06  6:49 ` marxin at gcc dot gnu.org
  0 siblings, 0 replies; 2+ messages in thread
From: marxin at gcc dot gnu.org @ 2020-04-06  6:49 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94491

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |marxin at gcc dot gnu.org
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2020-04-06

--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-04-06  6:49 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-05 11:04 [Bug driver/94491] New: -g2 debugging level is not documented slyfox at inbox dot ru
2020-04-06  6:49 ` [Bug driver/94491] " marxin at gcc dot gnu.org

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).