From: Andrew Cagney <ac131313@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [rfa/doco] Srink the overlay diagram
Date: Sun, 20 Jan 2002 21:11:00 -0000 [thread overview]
Message-ID: <3C4BA2E8.8090807@cygnus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 173 bytes --]
Hello,
One of the things giving overfull hboxes is JimB's overlay diagram. The
attached patch srinks it a little.
ok?
Andrew
PS: This diagram isn't on the 5.1 branch.
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 3935 bytes --]
2002-01-21 Andrew Cagney <ac131313@redhat.com>
* gdb.texinfo (How Overlays Work): Srink the overlay diagram.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.76
diff -p -r1.76 gdb.texinfo
*** gdb.texinfo 2002/01/20 11:59:38 1.76
--- gdb.texinfo 2002/01/21 05:07:10
*************** there.
*** 6420,6453 ****
@example
@group
! Data Instruction Larger
! Address Space Address Space Address Space
! +-----------+ +-----------+ +-----------+
! | | | | | |
! +-----------+ +-----------+ +-----------+<-- overlay 1
! | program | | main | | | load address
! | variables | | program | | overlay 1 |
! | and heap | | | ,---| |
! +-----------+ | | | | |
! | | +-----------+ | +-----------+
! +-----------+ | | | | |
! mapped --->+-----------+ / +-----------+<-- overlay 2
! address | overlay | <-' | overlay 2 | load address
! | area | <-----| |
! | | <---. +-----------+
! | | | | |
! +-----------+ | | |
! | | | +-----------+<-- overlay 3
! +-----------+ `--| | load address
! | overlay 3 |
! | |
! +-----------+
! | |
! +-----------+
! To map an overlay, copy its code from the larger address space
! to the instruction address space. Since the overlays shown here
! all use the same mapped address, only one may be mapped at a time.
@end group
@end example
--- 6420,6452 ----
@example
@group
! Data Instruction Larger
! Address Space Address Space Address Space
! +-----------+ +-----------+ +-----------+
! | | | | | |
! +-----------+ +-----------+ +-----------+<-- overlay 1
! | program | | main | | | load address
! | variables | | program | ,----| overlay 1 |
! | and heap | | | | | |
! +-----------+ | | | +-----------+
! | | +-----------+ | | |
! +-----------+ | | | +-----------+<-- overlay 2
! | | | | | load address
! mapped --->+-----------+ | .-| overlay 2 |
! address | overlay | <-' | | |
! | area | <---' +-----------+
! | | <---. | |
! +-----------+ | +-----------+<-- overlay 3
! | | | | | load address
! +-----------+ `--| overlay 3 |
! | |
! +-----------+
! | |
! +-----------+
! To map an overlay, copy its code from the larger address space to the
! instruction address space. Since the overlays shown here all use the
! same mapped address, only one may be mapped at a time.
@end group
@end example
next reply other threads:[~2002-01-21 5:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-20 21:11 Andrew Cagney [this message]
2002-01-21 1:59 ` Eli Zaretskii
2002-01-21 11:46 ` Andrew Cagney
2002-01-22 1:13 ` Eli Zaretskii
2002-01-24 18:55 ` Jim Blandy
2002-01-29 7:58 ` Andrew Cagney
2002-01-29 13:58 ` Andrew Cagney
2002-02-07 15:51 ` Andrew Cagney
2002-01-24 18:54 ` Jim Blandy
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=3C4BA2E8.8090807@cygnus.com \
--to=ac131313@cygnus.com \
--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