From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Paul_Koning@dell.com, gdb-patches@sourceware.org, pmuldoon@redhat.com
Subject: Re: [doc patch] compile: missing bits [Re: [PATCH v2 7/9] compile: New 'compile print']
Date: Thu, 09 Apr 2015 18:12:00 -0000 [thread overview]
Message-ID: <83pp7ddvcq.fsf@gnu.org> (raw)
In-Reply-To: <20150409173950.GA3400@host1.jankratochvil.net>
> Date: Thu, 9 Apr 2015 19:39:50 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Paul_Koning@dell.com, gdb-patches@sourceware.org, pmuldoon@redhat.com
>
> On Thu, 09 Apr 2015 09:39:46 +0200, Eli Zaretskii wrote:
> > So I think we should tell the story in the manual, yes.
>
> there were various missing bits for the 'compile' feature so adding them here.
Thanks.
> +@value{GDBN} needs to specify the right compilation options for the code
> +to be injected. In part to make its ABI compatible with the inferior
> +and in part to make the injected code compatible with GDB's injecting
> +process.
The second sentence is not a complete sentence; suggest to make it
part of the first (as in "...to be injected, in part to make its
ABI...").
Also, there's a bare "GDB" there.
> +@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?
> +@item set compile-args
> +@value{GDBN} contains default compilation options to set and possibly
> +override the options required for proper injection of the compiled code.
> +@end table
> +
> +@noindent
> +The options mentioned last can be specified with command:
> +
> +@table @code
> +@item set compile-args
This is slightly confusing. I suggest the following text instead:
@item compilation options set by @code{set compile-args}
@end table
@noindent
You can override compilation options using the following command:
@table @code
@item set compile-args
@cindex compile command options override
Set compilation options used for compiling and injecting code with the
@code{compile} commands. These options override any conflicting ones
from the target architecture and/or options stored during inferior
compilation.
@item show compile-args
Displays the current state of compilation options override.
This does not show all the options actually used during compilation,
use @ref{set debug compile} for that.
@end table
> +@value{GDBN} needs to find @value{NGCC} for the inferior being debugged which
> +may not be obvious for remote targets of different architecture than where
> +@value{GDBN} is running. Environment variable @code{PATH} (@code{PATH} from
> +shell that executed @value{GDBN}, not the one set by @value{GDBN}
> +command @code{set environment}. @xref{Environment}. @code{PATH} on
There's a right parenthesis missing here.
> +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,
Please don't up-case ARCH and OS, makeinfo will do that when needed.
Also, please use "---" instead of just one dash.
> +for pattern @code{s390x?}. @code{OS} is currently supported only for
> ^^^^^^^^^
@var{os}.
next prev parent reply other threads:[~2015-04-09 18:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 17:26 [PATCH v2 0/9] compile: compile print&printf Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 1/9] Code cleanup: Make parts of print_command_1 public Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 3/9] Code cleanup: compile: Constify some parameters Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 2/9] compile: Distribute scope, add scope_data Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 4/9] compile: Support relocation to GNU-IFUNCs Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 8/9] compile: New compile printf Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 5/9] compile: Use -Wall, not -w Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 7/9] compile: New 'compile print' Jan Kratochvil
2015-04-06 17:41 ` Eli Zaretskii
2015-04-06 17:49 ` Paul_Koning
[not found] ` <20150406175250.GA314@host1.jankratochvil.net>
2015-04-06 18:00 ` Paul_Koning
2015-04-08 20:03 ` Jan Kratochvil
2015-04-09 7:39 ` Eli Zaretskii
2015-04-09 17:40 ` [doc patch] compile: missing bits [Re: [PATCH v2 7/9] compile: New 'compile print'] Jan Kratochvil
2015-04-09 18:12 ` Eli Zaretskii [this message]
2015-04-10 8:09 ` Jan Kratochvil
2015-04-10 8:31 ` Eli Zaretskii
2015-04-10 8:35 ` [commit] " Jan Kratochvil
2015-04-10 14:09 ` Paul_Koning
2015-04-08 20:12 ` [PATCH v2 7/9] compile: New 'compile print' Paul_Koning
2015-04-08 20:33 ` Jan Kratochvil
2015-04-06 18:47 ` Jan Kratochvil
2015-04-11 19:20 ` Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 6/9] Code cleanup: compile: func_addr -> func_sym Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 9/9] compile: compile printf: gdbserver support Jan Kratochvil
2015-04-06 17:43 ` Eli Zaretskii
2015-04-11 19:23 ` Jan Kratochvil
2015-04-11 19:31 ` Eli Zaretskii
2015-04-11 19:46 ` obsolete: [PATCH v2 0/9] compile: compile print&printf Jan Kratochvil
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=83pp7ddvcq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Paul_Koning@dell.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pmuldoon@redhat.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