From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30487 invoked by alias); 28 Apr 2008 03:31:41 -0000 Received: (qmail 30478 invoked by uid 22791); 28 Apr 2008 03:31:41 -0000 X-Spam-Check-By: sourceware.org Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 28 Apr 2008 03:31:23 +0000 Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id C61B467276; Mon, 28 Apr 2008 03:31:21 +0000 (UTC) From: Mike Frysinger To: Eli Zaretskii Subject: Re: the "load" command and the .bss section Date: Mon, 28 Apr 2008 14:07:00 -0000 User-Agent: KMail/1.9.7 Cc: drow@false.org, gdb-patches@sourceware.org References: <200804270509.34308.vapier@gentoo.org> <200804271745.37849.vapier@gentoo.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1607570.PR3dBLIlgz"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200804272331.21219.vapier@gentoo.org> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00631.txt.bz2 --nextPart1607570.PR3dBLIlgz Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-length: 1486 On Sunday 27 April 2008, Eli Zaretskii wrote: > > From: Mike Frysinger > > Date: Sun, 27 Apr 2008 17:45:37 -0400 > > Cc: gdb-patches@sourceware.org > > > > ah, now that i know the intentions, may i suggest the following to the > > documentation. > > Thanks, but I'm afraid the text you suggested is not clear enough. > > > +The file is loaded according to the load addresses (rather than virtua= l) > > as > > How is "load address" opposed to "virtual address"? This requires > explanation. > > > +is specified in the executable. It is expected that the target system > > will +do the actual relocation, and in the process, handle such things = as > > setup of +allocated sections (e.g. the bss). > > This is also too cryptic to be useful. Can you (or someone else) > suggest a more elaborate description? E.g., what is ``relocation'' in > this context? and what other things besides .bss are expected to be > set up by loading? the load description in general implies the reader already has higher=20 knowledge of these details. i dont see the changes i propose affecting thi= s=20 in any way. i'm not sure expounding on the lower (and format-specific)=20 details being appropriate in this context as the final decision is up to th= e=20 target bfd, not gdb. if someone else wants to expand the description, go for it, but i'm fine wi= th=20 the small additions i've contributed, and i think the issues raised here ar= e=20 unrelated to the new text. -mike --nextPart1607570.PR3dBLIlgz Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. Content-length: 827 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iQIVAwUASBVFCUFjO5/oN/WBAQIgbA//dPkmmHGQQwHs+cAEyXbZ6zMixXOR3R5K m3Xquw2JYi/gOxH9s4SOkB/FNrHs6PlIzMMrGAaCh6NTcHGn76nkXBZ0gCvR5RNF 6h2hMAfrdAh57/EievQ+Jbi2SEJOqqBcefD2NUocDJUr/H2g6xk5P3pxehTTjt7z GeLFFJSnQnv42lNEjTNnPMQuxDhMzg1t2fk/nVTTPl0ouOFCpaAN06t/KJ08z2tL VSJ5TWgpIujnNyAz9lDfKNYdbHfM3uOcuLjiUwGKLzyiUYlxxbqVu4A+ezxJ5WXt aFGxeonAYUogKk0VwuzIIHOrpGtqfobSXTMFsJ5YzrrDRrLuXjEWe4wYUhkfSL17 mR3iQR1r+xXU/UvHy7Kq9QYg1rw4Wj/OJKqq2aiEy58jZsVeqRghpBl5tLlXTDJh jaUlP22mkezeAzclJTlttxWUybvnQotziG1yjv6n0VJpX4v5IObY6osczwr9jaqJ d832BuI5osg6iEPHYUtgB9IxOZZtKkcwSqhoJC1hKP8m6Cs9mgfWBTnbbZnaYIp8 l5NWFW9lqDaPpm/h6IDRRrkwq6735NumfkbPaahcFyIjn/kKPbGJKPU0ngZvy2wT /C/7xZvHLjrRTFUp7q7DgnJOHhK/4d2i+buuqIHkKsCGcgr6hqW7aaJZPN0KHQFq MbRsExnnkxU= =XdCY -----END PGP SIGNATURE----- --nextPart1607570.PR3dBLIlgz--