From: Eli Zaretskii <eliz@gnu.org>
To: Nick Ing-Simmons <nik@tiuk.ti.com>
Cc: gcc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, Russ Allbery <rra@stanford.edu>
Subject: Re: Strange strings in GCC compiled code
Date: Wed, 08 Sep 1999 04:25:00 -0000 [thread overview]
Message-ID: <199909081123.HAA30264@mescaline.gnu.org> (raw)
In-Reply-To: <199909080848.EAA25629@mescaline.gnu.org>
> But if (as is likely) binutils seeks down the file and does a write
> then junk is exposed if not overwritten.
I don't think Binutils work this way, at least not on all platforms.
Also, if this *does* happen, the junk usually comes from memory, not
from the disk.
WARNING: multiple messages have this Message-ID
From: Eli Zaretskii <eliz@gnu.org>
To: Nick Ing-Simmons <nik@tiuk.ti.com>
Cc: gcc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, Russ Allbery <rra@stanford.edu>
Subject: Re: Strange strings in GCC compiled code
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <199909081123.HAA30264@mescaline.gnu.org> (raw)
Message-ID: <19990930180200.Zr9Kj4ZK-rrkzMrS-gELlUhvDnKbW_DqCNYANiyWUec@z> (raw)
In-Reply-To: <199909080848.EAA25629@mescaline.gnu.org>
> But if (as is likely) binutils seeks down the file and does a write
> then junk is exposed if not overwritten.
I don't think Binutils work this way, at least not on all platforms.
Also, if this *does* happen, the junk usually comes from memory, not
from the disk.
next prev parent reply other threads:[~1999-09-08 4:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-07 15:52 Nimar Arora
1999-09-07 16:21 ` Russ Allbery
1999-09-30 18:02 ` Russ Allbery
1999-09-08 1:46 ` Eli Zaretskii
1999-09-30 18:02 ` Eli Zaretskii
1999-09-08 1:50 ` Eli Zaretskii
1999-09-08 2:10 ` Nick Ing-Simmons
1999-09-30 18:02 ` Nick Ing-Simmons
1999-09-08 4:25 ` Eli Zaretskii [this message]
1999-09-30 18:02 ` Eli Zaretskii
1999-09-30 18:02 ` Eli Zaretskii
1999-09-30 18:02 ` Nimar Arora
1999-09-08 13:32 Nimar Arora
1999-09-08 14:39 ` Mumit Khan
1999-09-30 18:02 ` Mumit Khan
1999-09-30 18:02 ` Nimar Arora
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=199909081123.HAA30264@mescaline.gnu.org \
--to=eliz@gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=nik@tiuk.ti.com \
--cc=rra@stanford.edu \
/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).