From: Wolfgang Denk <wd@denx.de>
To: Carlo Parravicini <c.parravicini@sehitaly.com>
Cc: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: ELDK 3.0 C++ Problem
Date: Thu, 20 May 2004 18:14:16 +0200 [thread overview]
Message-ID: <20040520161421.C7222C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 20 May 2004 16:02:44 +0200." <200405201602.44480.c.parravicini@sehitaly.com>
In message <200405201602.44480.c.parravicini@sehitaly.com> you wrote:
>
> > What makes you think so? I bet a case of beer that the 'new" returned
> > just fine, and that your program segfaulted in memset() instead.
>
> Lost the beer, the code is wrong but the segfaulted is in the "new"
> (checked with a printf before the memset & also with gdb eh eh)
No. The new returns just fine in my test. The segfault happens in the
memset() call when you write to memory that you don't own. I tested
it.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The Buddha, the Godhead, resides quite as comfortably in the circuits
of a digital computer or the gears of a cycle transmission as he does
at the top of a mountain or in the petals of a flower.
- R. Pirsig, "Zen and the Art of Motorcycle Maintenance"
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-20 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 15:57 ELDK 3.0 C++ Problem Carlo Parravicini
2004-05-19 17:56 ` Wolfgang Denk
2004-05-20 14:02 ` Carlo Parravicini
2004-05-20 16:14 ` Wolfgang Denk [this message]
-- 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=20040520161421.C7222C109F@atlas.denx.de \
--to=wd@denx.de \
--cc=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).