10-01-2002
When you malloc space you are attempting to increase the size of the data segment. Most unix system have some limit on the max size of a data segment often controlled by a kernel parameter called maxdsize or something like that. Additional you need to have enough resources (mostly swap area) to handle the additional virtual memory.
On every unix system in existence, if you malloc a MB of memory in a loop you will eventually fail. And if your program starts out with a very large data segment it is certainly possible that won't even be able to malloc one MB.
10 More Discussions You Might Find Interesting
1. Programming
1 . Thanks everyone who read the post.
2 . the programe is that :
#include <stdio.h>
#include <string.h>
void do_it(char *p)
{
p = (char *) malloc(100);
(void )strcpy(p,"1234");
}
int main(void)
{
char *p;
do_it(p);
(void )printf("p = %s \n",p); (1 Reply)
Discussion started by: chenhao_no1
1 Replies
2. Programming
hello sir
since by mentioning a integer pointer and storing the integers
by incrementing the pointer value
then what is the purpose of malloc?
u can decalre it as
in t *p;
several integers can be stored by incrementing the value of p,
hence what is the diffrence between this... (2 Replies)
Discussion started by: rajashekaran
2 Replies
3. Programming
Bit of a long one this
I am running the code below and I am getting a bus error when trying to make a struct member equal a variable. I stepped through the program in dbx and got the following. The structs of interest is raw_txns and la_ins_bkhead
Entered while loop in process()
t@1 (l@1)... (2 Replies)
Discussion started by: handak9
2 Replies
4. UNIX for Dummies Questions & Answers
Can someone tell me what this means????? :confused:
Catastrophe in malloc: sbrk()error 1b
IOT/Abort trap (coredump)
Thanks! (1 Reply)
Discussion started by: PAUL_ETTE
1 Replies
5. Programming
Hi!
I hope this is the correct forum to post the question even if I'm a newbie...
I am a C-newbie (and really on the edge to be a C-addict ;) ) and have a question.
When should I use malloc?
To state it differently, when should I NOT use malloc?
For instance, if I have an array of... (5 Replies)
Discussion started by: Tonje
5 Replies
6. AIX
Hi ,
I am facing some problem with C++ compiler ( version 5.0 ) on AIX machine ( 4.3 version).
When i run the following compile command,
cc -v -D< CONDITIONAL COMPILATION MACROS > -I< HEADER FILES SEARCH PATH >-qlanglvl=extended -g -qnoro -qnoroconst -c test_suman.cpp
For security... (0 Replies)
Discussion started by: suman_jakkula
0 Replies
7. Programming
Some one please explain me what is Dynamic memory allocation and the use of malloc() function.How do we allocate memory dynamically and also the other way? (3 Replies)
Discussion started by: rash123
3 Replies
8. UNIX for Advanced & Expert Users
Hey Guys
Some of my friends have got together and we are trying to write a basic kernel similar to Linux. I am trying to implement the malloc function in C and I am using a doubly linked list as the primary data structure. I need to allocate memory for this link list (duh...) and I don't feel... (2 Replies)
Discussion started by: rbansal2
2 Replies
9. Programming
Which one is faster among malloc and new?
My understanding is that since new also has to call constructors after allocating memory it must be slower than malloc.
Am I correct? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
10. UNIX for Dummies Questions & Answers
Good day! I'm a newbie in C. I'm trying to get an unlimited input from the user using malloc then printing the inputs after the user presses enter. My code works, but there's a warning that I don't know how to fix. Please help me. Thank you.
Here's my code:
#include <stdio.h>
#include... (6 Replies)
Discussion started by: eracav
6 Replies
LEARN ABOUT HPUX
bsdmalloc
bsdmalloc(3MALLOC) bsdmalloc(3MALLOC)
NAME
bsdmalloc - memory allocator
SYNOPSIS
cc [ flag ... ] file ... -lbsdmalloc [ library ... ]
char *malloc(size);
unsigned size;
int free( ptr);
char *ptr;
char *realloc( ptr, size);
char *ptr;
unsigned size;
These routines provide a general-purpose memory allocation package. They maintain a table of free blocks for efficient allocation and coa-
lescing of free storage. When there is no suitable space already free, the allocation routines call sbrk(2) to get more memory from the
system. Each of the allocation routines returns a pointer to space suitably aligned for storage of any type of object. Each returns a
null pointer if the request cannot be completed.
The malloc() function returns a pointer to a block of at least size bytes, which is appropriately aligned.
The free() function releases a previously allocated block. Its argument is a pointer to a block previously allocated by malloc() or real-
loc(). The free() function does not set errno.
The realloc() function changes the size of the block pointed to by ptr to size bytes and returns a pointer to the (possibly moved) block.
The contents will be unchanged up to the lesser of the new and old sizes. If the new size of the block requires movement of the block, the
space for the previous instantiation of the block is freed. If the new size is larger, the contents of the newly allocated portion of the
block are unspecified. If ptr is NULL, realloc() behaves like malloc() for the specified size. If size is 0 and ptr is not a null pointer,
the space pointed to is freed.
The malloc() and realloc() functions return a null pointer if there is not enough available memory. They return a non-null pointer if size
is 0. These pointers should not be dereferenced. When realloc() returns NULL, the block pointed to by ptr is left intact. Always cast the
value returned by malloc() and realloc().
If malloc() or realloc() returns unsuccessfully, errno will be set to indicate the following:
ENOMEM size bytes of memory cannot be allocated because it exceeds the physical limits of the system.
EAGAIN There is not enough memory available at this point in time to allocate size bytes of memory; but the application could try
again later.
Using realloc() with a block freed before the most recent call to malloc() or realloc() results in an error.
Comparative features of the various allocation libraries can be found in the umem_alloc(3MALLOC) manual page.
brk(2), malloc(3C), malloc(3MALLOC), mapmalloc(3MALLOC), umem_alloc(3MALLOC)
WARNINGS
Use of libbsdmalloc renders an application non-SCD compliant.
The libbsdmalloc routines are incompatible with the memory allocation routines in the standard C-library (libc): malloc(3C), alloca(3C),
calloc(3C), free(3C), memalign(3C), realloc(3C), and valloc(3C).
21 Mar 2005 bsdmalloc(3MALLOC)