From: Carlo Parravicini <c.parravicini@sehitaly.com>
To: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: ELDK 3.0 C++ Problem
Date: Wed, 19 May 2004 17:57:48 +0200 [thread overview]
Message-ID: <200405191757.48552.c.parravicini@sehitaly.com> (raw)
Hi all,
have anybody problems using ELDK3.0 ppc_8xx-g++ cross-compiler(x86) on 'new'
function?
I try to run a stupid program like that on a linux 2.4.4 (previus ELDK 2.1) &
linux 2.4.24 (ELDK 3.0)
//=================================================
#include <iostream>
#include <string.h>
int main (int argc, char **argv)
{
int *p = new int (10000);
memset ( p, 0, 10000);
if (p == NULL)
std::cout << "Allocation error\n";
else
std::cout << "OK.\n";
return 0;
//=================================================
ppc_8xx-g++ =Wall cpp.cpp -o cpp
ldd cpp->
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x0ff12000)
libm.so.6 => /lib/libm.so.6 (0x0fe46000)
libc.so.6 => /lib/libc.so.6 (0x0fce7000)
/lib/ld.so.1 => /lib/ld.so.1 (0x30000000)
Both give me a segmentation fault on 'new' execution
The same using a malloc compiled in 'C' mode runs
Previous version of ELDK works fine
Any other have c++ compiling problems or have compiled c++ code successfuly?
email: carlo@sehitaly.com
http://www.sehitaly.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-05-19 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 15:57 Carlo Parravicini [this message]
2004-05-19 17:56 ` ELDK 3.0 C++ Problem Wolfgang Denk
2004-05-20 14:02 ` Carlo Parravicini
2004-05-20 16:14 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-05-19 21:38 Gosha, Michael (Michael)
2004-05-19 23:17 ` Wolfgang Denk
2004-05-21 16:46 Wells, Charles
2004-05-21 18:26 ` Mark Chambers
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=200405191757.48552.c.parravicini@sehitaly.com \
--to=c.parravicini@sehitaly.com \
--cc=linuxppc-embedded@lists.linuxppc.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).