From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches@sources.redhat.com
Cc: eliz@is.elta.co.il
Subject: [RFA] Documentation -- 'set trust-readonly-sections'
Date: Thu, 31 Jan 2002 11:35:00 -0000 [thread overview]
Message-ID: <200201311928.g0VJSiY30284@reddwarf.cygnus.com> (raw)
Eli, is this OK?
2002-01-30 Michael Snyder <msnyder@redhat.com>
* gdb.texinfo (set trust-readonly-sections): Document.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.82
diff -p -r1.82 gdb.texinfo
*** gdb.texinfo 2002/01/27 09:34:24 1.82
--- gdb.texinfo 2002/01/31 04:11:31
*************** COFF shared library information.
*** 9410,9415 ****
--- 9410,9430 ----
Section contains common symbols.
@end table
@end table
+ @kindex set trust-readonly-sections
+ @item set trust-readonly-sections on
+ Tell @value{GDBN} that readonly sections in your object file
+ really are read-only (ie. that their contents will not change).
+ In that case, @value{GDBN} can fetch values from these sections
+ out of the object file, rather than from the target program.
+ For some targets (notably embedded ones), this can be a significant
+ enhancement to debugging performance.
+
+ The default is off.
+
+ @item set trust-readonly-sections off
+ Tell @value{gdbn} not to trust readonly sections. This means that
+ the contents of the section might change while the program is running,
+ and must therefore be fetched from the target when needed.
@end table
All file-specifying commands allow both absolute and relative file names
next reply other threads:[~2002-01-31 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 11:35 Michael Snyder [this message]
2002-02-01 1:07 ` Eli Zaretskii
2002-02-01 9:22 ` Michael Snyder
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=200201311928.g0VJSiY30284@reddwarf.cygnus.com \
--to=msnyder@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.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