This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

GCC 3.2.1 problems?

From: Fredrik Hederstierna <fredrik at wespot dot com>
To: Brian Murphy <brm at tt dot dk>
Cc: ecos-discuss at sources dot redhat dot com, Jonathan Larmour <jifl at eCosCentric dot com>
Date: Fri, 07 Feb 2003 10:37:31 +0100
Subject: [ECOS] GCC 3.2.1 problems?
References: <20030206181030.16610.qmail@web11405.mail.yahoo.com> <3E42E390.4080000@eCosCentric.com> <3E435F2B.9030607@tt.dk>

We switched from eCos 1.3.1 to eCos 2 some months ago, but eCos 2 started
to crash our system, sometimes after some hours, caused by what seemed to
be stack memory trashing.

Now we changed GCC 3.2.1 to GCC 3.2.2 and to problems disappeared!
It might be caused by problems in GCC 3.2.1, so if your system crashes in
mysterious ways with GCC 3.2.1, try using GCC 3.2.2, binutils 2.13.1,
newlib 1.11.0. It works fine with our system (ARM7-based). (But ofcourse
its GCC 2.95.2 which is the supported one by RH).

Best Regards,
/Fredrik Hederstierna



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

References:
- undefined reference to `operator new(unsigned)'
  - From: Calvin Du
- Re: undefined reference to `operator new(unsigned)'
  - From: Jonathan Larmour
- Re: undefined reference to `operator new(unsigned)'
  - From: Brian Murphy

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]