01-29-2002
Like I said malloc/free will never shrink the process. But also, they aren't prepared for you to sneak in and do it for them. So malloc() is assuming that the process is still the same size it left it. And when it tries to reference the now non-existant space that it previously allocated, you get a SIGSEGV.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I need some advise.
I have an application server running several applications. When I try and start a particular application when the others are running I receive the following. This is appearing in the core file that is created.
... (1 Reply)
Discussion started by: dbrundrett
1 Replies
2. UNIX and Linux Applications
We are currently running HP-UX 11 as our database server. The database is Progress version 9.1C.
As of late, some of our batch processes that run on the UNIX db server are erroring out because of what appear to be memory issues(at least according to Progress). The db error messages indicate... (0 Replies)
Discussion started by: eddiej
0 Replies
3. HP-UX
I don't know if this is better suited for the application section, but here goes.
We are currently running HP-UX 11 as our database server. The database is Progress version 9.1C.
As of late, some of our batch processes that run on the UNIX db server are erroring out because of what appear to... (3 Replies)
Discussion started by: eddiej
3 Replies
4. Programming
Hi everbody, i have a problem with shared memory and child-processes in C (unix).
I have a server that do forks to create (N) child processes. This processes work with a shared "stuct" thanks to shared memory and a semaphore. The problem is when a child modify the shared memory and the others... (2 Replies)
Discussion started by: hurricane86
2 Replies
5. Programming
Hi, I need to put in shared memory a list made with object of this structure:
typedef struct Obj{
char objname;
struct Obj *nextObj;
}Object
I've filled my list with (for example) 10 elements, but when i try to put it in shared memory to be read by another process i get segmentation fault... (6 Replies)
Discussion started by: BeNdErR
6 Replies
6. Solaris
I work with a network management tool, which, for various reasons, is installed on a solaris server.This is a Sunfire T2000 server with 16 CPUs and 8GB of RAM. I have installed a Solaris 10 ZFS and 8GB swap. From the beginning I had problems with memory occupation that it rises progressively to 95%... (4 Replies)
Discussion started by: drusa79
4 Replies
7. Shell Programming and Scripting
I am newbe to unix.
I have a very serious problem on my server.
I have a java application running, and all day on Monday morning, the process that is associated with this java is locked.
Usually I doing a shutdown by the shutdown java command , you have to kill the process with the kill-kill... (1 Reply)
Discussion started by: jjoottaa
1 Replies
8. Red Hat
Hi all,
i have some doubts in a situation that i fail to get an answer in Google.
I have a solaris 10 nfs server and 5 centos 6.0 nfs clients.
The problem/situation is that in the clients the free memory is "disappearing" along the time (passing to used)..and it gets free if i umount the... (5 Replies)
Discussion started by: blast
5 Replies
9. Solaris
We have a 6000 chassis with three blades in it. Two of the blades have "Oracle/Sun" memory in them with no complaints. The third blade is populated with Dataram dimms. That 3rd blade continues to flag a slot bad. Oracle has said they would not support the blade with Dataram memory it it. I didn't... (1 Reply)
Discussion started by: brownwrap
1 Replies
10. AIX
Hi All, Just loaded AIX 6.1 and then got Firefox running on the workstation. To test out I wanted to download some small files from 'Perlz', and during this I'm told there's not enough room in the Downloads folder. What do I do to resize folders from the default and generally move memory around? In... (3 Replies)
Discussion started by: Box_the_Jack_in
3 Replies
LEARN ABOUT XFREE86
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)