Re: Windows DLL support update (a bit slimmer version)

Daniel Jacobowitz
2007-10-24T21:06:43Z

On Wed, Oct 24, 2007 at 09:50:05PM +0200, Eli Zaretskii wrote:
> "Support to support"? Can you find a better wording? Something like
> "must be linked with the Expat library to support ..."?

Thanks for noticing. Here's one using that better wording, which I've
checked in - I'd made this blunder elsewhere too.

--
Daniel Jacobowitz
CodeSourcery

2007-10-24 Daniel Jacobowitz <dan@codesourcery.com>

* gdb.texinfo (Files): Correct formatting. Mention Expat
requirement.
(Requirements for Building GDB): Expand the list of Expat
uses.
(Library List Format, Memory Map Format): Mention Expat.
(Target Descriptions): Update Expat wording.

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.439
diff -u -p -r1.439 gdb.texinfo
--- gdb.texinfo 16 Oct 2007 17:36:51 -0000 1.439
+++ gdb.texinfo 24 Oct 2007 21:04:19 -0000
@@ -11795,9 +11795,13 @@ as arguments. @value{GDBN} always conve
name and remembers it that way.

@cindex shared libraries
-@value{GDBN} supports GNU/Linux, MS-Windows, HP-UX, SunOS, SVr4, Irix,
+@anchor{Shared Libraries}
+@value{GDBN} supports @sc{gnu}/Linux, MS-Windows, HP-UX, SunOS, SVr4, Irix,
and IBM RS/6000 AIX shared libraries.

+On MS-Windows @value{GDBN} must be linked with the Expat library to support
+shared libraries. @xref{Expat}.
+
@value{GDBN} automatically loads symbol definitions from shared libraries
when you use the @code{run} command, or when you examine a core file.
(Before you issue the @code{run} command, @value{GDBN} does not understand
@@ -22176,8 +22180,18 @@ The @file{configure} script will search
standard locations; if it is installed in an unusual path, you can
use the @option{--with-libexpat-prefix} option to specify its location.

-Expat is used for remote protocol memory maps (@pxref{Memory Map Format})
-and for target descriptions (@pxref{Target Descriptions}).
+Expat is used for:
+
+@itemize @bullet
+@item
+Remote protocol memory maps (@pxref{Memory Map Format})
+@item
+Target descriptions (@pxref{Target Descriptions})
+@item
+Remote shared library lists (@pxref{Library List Format})
+@item
+MS-Windows shared libraries (@pxref{Shared Libraries})
+@end itemize

@end table

@@ -25698,6 +25712,9 @@ where the library was loaded in memory.
addresses, not relocation offsets; they do not depend on the library's
link-time base addresses.

+@value{GDBN} must be linked with the Expat library to support XML
+library lists. @xref{Expat}.
+
A simple memory map, with one loaded library relocated by a single
offset, looks like this:

@@ -25731,7 +25748,12 @@ memory map.

The memory map is obtained using the @samp{qXfer:memory-map:read}
(@pxref{qXfer memory map read}) packet and is an XML document that
-lists memory regions. The top-level structure of the document is shown below:
+lists memory regions.
+
+@value{GDBN} must be linked with the Expat library to support XML
+memory maps. @xref{Expat}.
+
+The top-level structure of the document is shown below:

@smallexample
<?xml version="1.0"?>
@@ -25841,8 +25863,8 @@ actually describe its own features. Thi
processor variants it has never seen before --- to the extent that the
descriptions are accurate, and that @value{GDBN} understands them.

-@value{GDBN} must be compiled with Expat support to support XML target
-descriptions. @xref{Expat}.
+@value{GDBN} must be linked with the Expat library to support XML
+target descriptions. @xref{Expat}.

@menu
* Retrieving Descriptions:: How descriptions are fetched from a target.