On Thu, 09 Apr 2015 20:12:21 +0200, Eli Zaretskii wrote:
> > +@value{NGCC} (since version 4.7) stores the options used for compilation
> > +into @code{DW_AT_producer} part of DWARF debugging information according
> > +to the @value{NGCC} option @code{-grecord-gcc-switches}.  One has to
> > +explicitly specify @code{-g} during inferior compilation otherwise
> > +@value{NGCC} produces no DWARF.
> 
> Hmm...  Are you sure -g always produces DWARF?  Maybe we should say
> that for targets where DWARF is not the default, -gdwarf-N should be
> used, and also that -gstabs etc. should _not_ be used?

While you are technically right I do not think it is appropriate to mention it
that way.

When some platform is still using -gstabs by default (is there any?) there are
probably some serious reasons for it - such as some old debugging / crash
analysing tools incompatible with DWARF.  Using -gdwarf-X may do more harm
than good there IMO; unless one really knows what s/he is doing and then one
does not need to read this doc.

I have just added:
	This feature is only relevant for 
	platforms where @code{-g} produces DWARF by default, otherwise one may
	try to enforce DWARF by using @code{-gdwarf-4}.


> > +Specifically @code{PATH} is searched for binaries matching regular expression
> > +@code{@var{ARCH}(-[^-]*)?-@var{OS}-gcc} according to the inferior target being
> > +debugged.  @code{@var{ARCH}} is processor name - multiarch is supported,
[...]
> > +for pattern @code{s390x?}.  @code{OS} is currently supported only for
> >                              ^^^^^^^^^
> 
> @var{os}.

Not sure if @code{@var{os}} is the same as @var{os}, used only @var{os}.


Thanks,
Jan