From: Luciano Miguel Ferreira Rocha <luciano@lsd.di.uminho.pt>
To: Matthew Studley <matthew.studley@uwe.ac.uk>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: gcc : cpp Memory Exhausted
Date: Wed, 24 Sep 2003 23:23:54 +0100 [thread overview]
Message-ID: <20030924222354.GA29626@lsd.di.uminho.pt> (raw)
In-Reply-To: <010701c382ae$5490ec10$caba0ba4@uwe.ac.uk>
On Wed, Sep 24, 2003 at 04:12:54PM +0100, Matthew Studley wrote:
> I have 'solved' the problem; I was just compiling one of the source files, I
> deleted all compiled output and recompiled all the source. No problem!
>
> This is bizarre!
>
> I have no idea what was causing this though, and would really appreciate any
> ideas!
I don't know the exact reason, but I'l give some suggestions:
1. recursive #include, as when a.h #includes "b.h", and b.h #includes "a.h"
or just a.h #includes "a.h"...
2. memory corruption. the compilation of all sources could had caused the
corrupted cache to be discarded.
3. corruption of disk transfers
(by means of an invalid selected DMA or ilegal cable)
Regards,
Luciano Rocha
prev parent reply other threads:[~2003-09-24 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030922104825.81134.qmail@web20002.mail.yahoo.com>
[not found] ` <003501c3811f$610395a0$ed64a8c0@descartes>
[not found] ` <3F702813.8030200@gsecone.com>
2003-09-23 16:07 ` Switching between foreground and background John T. Williams
2003-09-23 16:19 ` guide to inline assembly palash kasodhan
2003-09-23 17:57 ` Progga
2003-09-23 17:24 ` Switching between foreground and background Mariano Moreyra
2003-09-24 14:36 ` gcc : cpp Memory Exhausted Matthew Studley
2003-09-24 15:12 ` Matthew Studley
2003-09-24 22:23 ` Luciano Miguel Ferreira Rocha [this message]
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=20030924222354.GA29626@lsd.di.uminho.pt \
--to=luciano@lsd.di.uminho.pt \
--cc=linux-c-programming@vger.kernel.org \
--cc=matthew.studley@uwe.ac.uk \
/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 NNTP newsgroup(s).