08-16-2011
My best advice would be for you to switch to a 64 bit OS and application. You still don't give a clue about the allocated area sizes but I suspect that your process virtual memory is too fragmented for a contiguous segment large enough to be available.
10 More Discussions You Might Find Interesting
1. Programming
Can Any body give me a exampla which has the usage of realloc
i want a function which uses realloc & increases /decreases the size of a pointer (0 Replies)
Discussion started by: wojtyla
0 Replies
2. Programming
Hello,
my program works properly but valgrind tells me I am not freeing allocated memory. I think the problem is in realloc.
I am pretty sure I do something wrong with realloc, because I changed it a bit and valgrind noticed less errors (that the program wasn't working properly with less errors... (3 Replies)
Discussion started by: samciz
3 Replies
3. Programming
hi,
I'm using gcc version 3.4.6 on a Red Hat system... (not sure how to determine version of glibc)
when i run the following, i get:
glibc detected *** realloc(): invalid next size: 0x0804a170
I'm not sure what is wrong. The error happens on the second iteration of
the while loop.... (3 Replies)
Discussion started by: Andrewkl
3 Replies
4. Programming
N00B here. This function would be easier using a char pointer along with free. But I wish to learn how to use char static pointers (they do not require free, right ?).
How do I erase the content of a static pointer ? Terminating the string works but the static pointer's content is not being... (4 Replies)
Discussion started by: limmer
4 Replies
5. Programming
Why when using realloc, john is reversed 3 times but not the other 2 names ? But if I use malloc, then the 3 names are reversed correctly ? (but then there is a memory leak)
How can I reverse all 3 names without a memory leak ?
char *BUFFER = NULL;
char *STRREVERSE(const char *STRING)
{... (5 Replies)
Discussion started by: cyler
5 Replies
6. Programming
Hi,
I am seeing varying results about, when realloc() fails in reallocation.
Which one is correct out of the below?
a) realloc() maintains the original pointer (i.e) the original pointer is left unaltered/untouched but relloc() returns the NULL value.
b) original buffer pointer is lost... (3 Replies)
Discussion started by: royalibrahim
3 Replies
7. Programming
Hi all
I'm trying to use someone else's software, which has a realloc that fails in it. This is probably due to memory limitations, as it only happens when I use this software on huge datasets.
First question : how to diagnose if it's a soft or hard limitation? I mean, if it's due to my... (10 Replies)
Discussion started by: jossojjos
10 Replies
8. Programming
b = realloc(a, 1000);
if realloc succeeds and b!=a (not in-place replacement), does realloc automatically free a or I should free both a and b afterwards?
thank you! (5 Replies)
Discussion started by: bashuser2
5 Replies
9. UNIX for Dummies Questions & Answers
#include <malloc.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
int*
allocat_array(void)
{
int *array;
int tmp;
int n_values = 0 ;
array = malloc(sizeof(int));
if(array == NULL)
return NULL;
while(scanf("%d",&tmp) != EOF)
{
... (1 Reply)
Discussion started by: vincent__tse
1 Replies
10. Programming
Hi everyone,
i made this program. is a simple one for practising malloc, realloc and structs.
I have a struct named shop as global variable in which i take the size of the matrix from the keyboard and after i malloc it.
I insert the values with the fullarray() and after i print the matrix with... (7 Replies)
Discussion started by: giampoul
7 Replies
LEARN ABOUT REDHAT
mremap
MREMAP(2) Linux Programmer's Manual MREMAP(2)
NAME
mremap - re-map a virtual memory address
SYNOPSIS
#include <unistd.h>
#include <sys/mman.h>
void * mremap(void *old_address, size_t old_size , size_t new_size, unsigned long flags);
DESCRIPTION
mremap expands (or shrinks) an existing memory mapping, potentially moving it at the same time (controlled by the flags argument and the
available virtual address space).
old_address is the old address of the virtual memory block that you want to expand (or shrink). Note that old_address has to be page
aligned. old_size is the old size of the virtual memory block. new_size is the requested size of the virtual memory block after the
resize.
The flags argument is a bitmap of flags.
In Linux the memory is divided into pages. A user process has (one or) several linear virtual memory segments. Each virtual memory seg-
ment has one or more mappings to real memory pages (in the page table). Each virtual memory segment has its own protection (access
rights), which may cause a segmentation violation if the memory is accessed incorrectly (e.g., writing to a read-only segment). Accessing
virtual memory outside of the segments will also cause a segmentation violation.
mremap uses the Linux page table scheme. mremap changes the mapping between virtual addresses and memory pages. This can be used to
implement a very efficient realloc.
FLAGS
MREMAP_MAYMOVE
indicates if the operation should fail, or change the virtual address if the resize cannot be done at the current virtual address.
RETURN VALUE
On success mremap returns a pointer to the new virtual memory area. On error, -1 is returned, and errno is set appropriately.
ERRORS
EINVAL An invalid argument was given. Most likely old_address was not page aligned.
EFAULT "Segmentation fault." Some address in the range old_address to old_address+old_size is an invalid virtual memory address for this
process. You can also get EFAULT even if there exist mappings that cover the whole address space requested, but those mappings are
of different types.
EAGAIN The memory segment is locked and cannot be re-mapped.
ENOMEM The memory area cannot be expanded at the current virtual address, and the MREMAP_MAYMOVE flag is not set in flags. Or, there is
not enough (virtual) memory available.
NOTES
With current glibc includes, in order to get the definition of MREMAP_MAYMOVE, you need to define _GNU_SOURCE before including
<sys/mman.h>.
CONFORMING TO
This call is Linux-specific, and should not be used in programs intended to be portable. 4.2BSD had a (never actually implemented)
mremap(2) call with completely different semantics.
SEE ALSO
getpagesize(2), realloc(3), malloc(3), brk(2), sbrk(2), mmap(2)
Your favorite OS text book for more information on paged memory. (Modern Operating Systems by Andrew S. Tannenbaum, Inside Linux by Ran-
dolf Bentson, The Design of the UNIX Operating System by Maurice J. Bach.)
Linux 1.3.87 1996-04-12 MREMAP(2)