From: "Matthew Studley" <matthew.studley@uwe.ac.uk>
To: Matthew Studley <matthew.studley@uwe.ac.uk>,
linux-c-programming@vger.kernel.org
Subject: Re: memory exhausted
Date: Tue, 25 Nov 2003 15:10:32 -0000 [thread overview]
Message-ID: <001701c3b366$45219250$caba0ba4@uwe.ac.uk> (raw)
In-Reply-To: 000501c3b363$abe79140$caba0ba4@uwe.ac.uk
Well I clearly have a brain like a seive - I now remember that I've had this
problem before. To solve it I deleted all object files and recompiled the
entire application. No problem. Your guesses why this happens would be
very interesting!
regards
matt
<phew> panic over!
----- Original Message -----
From: Matthew Studley <matthew.studley@uwe.ac.uk>
To: <linux-c-programming@vger.kernel.org>
Sent: Tuesday, November 25, 2003 2:51 PM
Subject: cpp: memory exhausted
> Hi all
>
> I am compiling some code using gcc. I have compiled the same code before,
> on the same platform, with the same compiler, on the same ... nothing's
> changed!
>
> But now I get the message:
>
> cpp: memory exhausted
>
> I have rebooted, physically switched off and on - still the same problem!
>
> help!
>
> please?
>
> Matt
> ==============================================
> Matthew Studley
>
> Intelligent Autonomous Systems Laboratory
>
> Faculty of Computing, Engineering
> and Mathematical Sciences
> Coldharbour Lane, Frenchay
> BS16 1QY
> United Kingdom
>
> tel : 07092 306548
> fax : 07092 306548
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
> This incoming email to UWE has been independently scanned for viruses and
any virus detected has been removed using McAfee anti-virus software
>
>
>
next prev parent reply other threads:[~2003-11-25 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 14:51 cpp: memory exhausted Matthew Studley
2003-11-25 15:10 ` Matthew Studley [this message]
2003-11-25 22:38 ` Thomas Steudten
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='001701c3b366$45219250$caba0ba4@uwe.ac.uk' \
--to=matthew.studley@uwe.ac.uk \
--cc=linux-c-programming@vger.kernel.org \
/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).