From: Kenji Arisawa <arisawa@ar.aichi-u.ac.jp>
To: 9front@9front.org
Subject: malloc
Date: Sun, 4 May 2014 14:24:14 +0900 [thread overview]
Message-ID: <94FC2DC4-E47A-4B93-80B4-F0B3F8E98E04@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <CAEAzY3-DawUsVh4ks6Z+KatuyM2f4Tg-mT5-F+RQ+0SKJhUBAw@mail.gmail.com>
It seems malloc() has a problem with large size allocation.
void
test1(void)
{
char *p, buf[256];
ulong i,n[16];
ulong MB = 1024*1024;
n[0] = 1024;
n[1] = 1024;
n[2] = 1024;
n[3] = 512;
n[4] = 0;
for(i = 0; n[i]; i++){
p = malloc(n[i]*MB);
print("%d %uldMB %08p\n",i,n[i],p);
if(p ==nil)
continue;
}
read(0,buf, sizeof(buf));
}
term% 6.out
0 1024MB 00401948
1 1024MB 404019b0
2 1024MB 80401a18
3 512MB c0401a80
# this is OK
void
test2(void)
{
char *p, buf[256];
ulong i,n[16];
ulong MB = 1024*1024;
n[0] = 3*1024+512;
n[1] = 0;
for(i = 0; n[i]; i++){
p = malloc(n[i]*MB);
print("%d %uldMB %08p\n",i,n[i],p);
if(p ==nil)
continue;
}
read(0,buf, sizeof(buf));
}
term% 6.out
0 3584MB 00000000
# this is NG
next prev parent reply other threads:[~2014-05-04 5:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 4:25 9FRONT "опен-сссл" Released sl
2014-04-28 10:52 ` cwfs fsmempercent arisawa
2014-04-28 17:08 ` [9front] " cinap_lenrek
2014-04-28 17:26 ` cinap_lenrek
2014-04-28 22:55 ` arisawa
2014-04-29 20:11 ` cinap_lenrek
2014-04-30 14:41 ` Kenji Arisawa
2014-04-30 20:14 ` cinap_lenrek
2014-05-01 10:39 ` 9pc64 arisawa
2014-05-01 11:07 ` [9front] 9pc64 Aram Hăvărneanu
2014-05-01 14:06 ` arisawa
2014-05-01 14:25 ` cinap_lenrek
2014-05-01 14:39 ` cinap_lenrek
2014-05-01 15:27 ` cinap_lenrek
2014-05-01 21:49 ` Kenji Arisawa
2014-05-01 21:51 ` cinap_lenrek
2014-05-01 23:22 ` Kenji Arisawa
2014-05-01 23:34 ` Kenji Arisawa
2014-05-02 0:22 ` cinap_lenrek
2014-05-02 11:02 ` Aram Hăvărneanu
2014-05-04 5:24 ` Kenji Arisawa [this message]
2014-05-04 8:22 ` [9front] malloc arisawa
2014-05-04 12:40 ` [9front] cwfs fsmempercent arisawa
2014-05-04 23:22 ` cinap_lenrek
2014-05-05 0:11 ` arisawa
2014-05-05 0:31 ` cinap_lenrek
2014-05-05 0:43 ` cinap_lenrek
2014-05-05 2:04 ` arisawa
2014-05-05 4:32 ` cinap_lenrek
2014-05-05 8:00 ` arisawa
2014-05-05 11:15 ` arisawa
2014-05-05 12:08 ` arisawa
2014-05-03 0:37 ` cinap_lenrek
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=94FC2DC4-E47A-4B93-80B4-F0B3F8E98E04@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9front@9front.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).