From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Ron Michael Khu <ronkhu@ntsp.nec.co.jp>
Cc: p.boehm@d-trust.net, linux-c-programming@vger.kernel.org
Subject: Re: Antwort: Re: Antwort: Re: -EFAULT during freeing a pointer to a structure
Date: Fri, 8 Oct 2004 15:59:38 +0200 [thread overview]
Message-ID: <20041008135938.GO5033@lug-owl.de> (raw)
In-Reply-To: <41669D5E.1050402@hq.ntsp.nec.co.jp>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
On Fri, 2004-10-08 21:59:58 +0800, Ron Michael Khu <ronkhu@ntsp.nec.co.jp>
wrote in message <41669D5E.1050402@hq.ntsp.nec.co.jp>:
> I may not know how u got away with it by using even values for maxnum,
> but almost everbody knows that an array created with N elements/slots in
> C,C++ or in java
> could only be safely accessed/manipulated via the indices 0...N-1
> (unless if u're an expert in memory manipulation)
Don't ever do that. While you may "survive" on one operating system
using a specific malloc library and a specific processor, you just loose
all portability. Just use the malloc functions as they were advertised
in their manual pages :-)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-08 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 12:27 Antwort: Re: Antwort: Re: -EFAULT during freeing a pointer to a structure p.boehm
2004-10-08 12:43 ` Jan-Benedict Glaw
2004-10-08 13:59 ` Ron Michael Khu
2004-10-08 13:59 ` Jan-Benedict Glaw [this message]
2004-10-08 14:07 ` Ron Michael Khu
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=20041008135938.GO5033@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-c-programming@vger.kernel.org \
--cc=p.boehm@d-trust.net \
--cc=ronkhu@ntsp.nec.co.jp \
/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).