From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul_Koning@dell.com, gdb-patches@sourceware.org, pmuldoon@redhat.com
Subject: [doc patch] compile: missing bits [Re: [PATCH v2 7/9] compile: New 'compile print']
Date: Thu, 09 Apr 2015 17:40:00 -0000 [thread overview]
Message-ID: <20150409173950.GA3400@host1.jankratochvil.net> (raw)
In-Reply-To: <83egntg37h.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 218 bytes --]
Hi Eli,
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,
Jan
[-- Attachment #2: 1 --]
[-- Type: text/plain, Size: 4053 bytes --]
gdb/doc/
2015-04-09 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.texinfo (Compiling and Injecting Code): Describe set debug
compile, show debug compile. New subsection Compilation options for
the compile command. New subsection Compiler search for the compile
command.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index d794893..ac50ea8 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -17223,6 +17223,66 @@ compile file /home/user/example.c
@end smallexample
@end table
+@noindent
+The process of compiling and injecting the code can be inspected using:
+
+@table @code
+@anchor{set debug compile}
+@item set debug compile
+@cindex compile command debugging info
+Turns on or off display of @value{GDBN} process of compiling and
+injecting the code. The default is off.
+
+@item show debug compile
+Displays the current state of displaying @value{GDBN} process of
+compiling and injecting the code.
+@end table
+
+@subsection Compilation options for the @code{compile} command
+
+@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.
+
+@noindent
+The options used, in increasing precedence:
+
+@table @asis
+@item target architecture and OS options (@code{gdbarch})
+These options depend on target processor type and target operating
+system, usually they specify at least 32-bit (@code{-m32}) or 64-bit
+(@code{-m64}) compilation option.
+
+@item compilation options recorded in the target
+@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.
+
+@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
+@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
+
@subsection Caveats when using the @code{compile} command
There are a few caveats to keep in mind when using the @code{compile}
@@ -17380,6 +17440,24 @@ Access to those variables will generate a compiler error which @value{GDBN}
will print to the console.
@end table
+@subsection Compiler search for the @code{compile} command
+
+@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
+@value{GDBN} host is searched for @value{NGCC} binary matching the
+target architecture and operating system.
+
+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,
+so for example both @code{i386} and @code{x86_64} targets look for pattern
+@code{(x86_64|i.86)} and both @code{s390} and @code{s390x} targets look
+for pattern @code{s390x?}. @code{OS} is currently supported only for
+pattern @code{linux(-gnu)?}.
+
@node GDB Files
@chapter @value{GDBN} Files
next prev parent reply other threads:[~2015-04-09 17:40 UTC|newest]
Thread overview: 30+ 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 4/9] compile: Support relocation to GNU-IFUNCs 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 3/9] Code cleanup: compile: Constify some parameters 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-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
2015-04-06 17:52 ` Jan Kratochvil
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 ` Jan Kratochvil [this message]
2015-04-09 18:12 ` [doc patch] compile: missing bits [Re: [PATCH v2 7/9] compile: New 'compile print'] Eli Zaretskii
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 8/9] compile: New compile printf Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 6/9] Code cleanup: compile: func_addr -> func_sym Jan Kratochvil
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=20150409173950.GA3400@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=Paul_Koning@dell.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).