problem with realloc( i think is gcc :/ )

10 More Discussions You Might Find Interesting

1. Red Hat

Installatin problem in installing gcc-4.9.0

Hi to all, i'm installing gcc-4.9.0 into my RedHat 6.4 pc. I configure like this :- # mkdir objdir # ./../gcc-4.9.0/configure # make and now having this problem :- checking for x86_64-unknown-linux-gnu-gcc... /software/gcc/objdir/./gcc/xgcc -B/software/gcc/objdir/./gcc/...

2. Programming

gcc problem

Hi, I just try to solve the problem why one app failing on box1 and runs ok on box2, they have diff gcc version as I see from /proc/version: box1:: 3.4.1 box2:: 4.1.2 It's RedHat 64b boxes, so I can not run some <make all> command on box1, do you think I need to upgrade (if I'm using...

3. Programming

Problem with static compiling - GCC

Hi guys. I want to compile three files: gcc -static main.c fib.c fib.h it is pure C i mean i use standard C library. but it gives me this error: /usr/bin/ld: cannot find -lc collect2: ld returned 1 exit status what should i do?

4. Solaris

gcc problem on Solaris

I just installed gcc from the latest package at sunfreeware.com using pkgadd. I write a simple 'Hello World!' program to test it. I try to compile it and I get this error: rockstar# gcc hello.c -o hello ld.so.1: gcc: fatal: libiconv.so.2: open failed: No such file or directory Killed I...

5. Red Hat

GCC version problem

I have a host PC and a target system . Host System -> gcc (3.2) Redhat linux kernel 2.4.20-8 , glibc 2.3 Target System -> gcc (4.1) Fedora linux kernel 2.6.18-1.2798.fc6, glibc 2.5 I would like to build test program that can be run on both systems --------------------------- ...

6. AIX

The problem after install gcc on AIX 5.3

The problem after install gcc on AIX 5.3 I download 5 rpm packages from IBM AIX Toolbox Download Page - Alphabetical Listing and install them. rpm -ivh gcc-4.0.0-1.aix5.3.ppc.rpm rpm -ivh libgcc-4.0.0-1.aix5.3.ppc.rpm rpm -ivh libstdcplusplus-4.0.0-1.aix5.3.ppc.rpm rpm -ivh...

7. Solaris

gcc 3.4 Regex problem

Hello All, I have been using String.h with gcc 2.95. Now I have upgraded to gcc 3.4. The support for String.h has been removed and I believe Regex.h support is also not inbuilt. So I tried to build my own library for String.h. I had to use Regex.h and rx.h for a succesful library compilation....

8. Programming

A problem of GCC

Hi mates, I am a new comer of this forums. I have a problem while using function "fread(buffer, size, number, file-pointer)" to read a binary file. While I used the "fread()" to read the binary file under Solaris UNIX System, it worked very well. But it gets a incorrect result...

9. Programming

gcc Link problem

I have some crypting functions in object-file - for example,func.o Main file,from where crypting functions called, named as main.cpp . "gcc main.cpp -o main func.o" print "undefined reference to ... " But if I rename main.cpp to main.c and execute "gcc main.c -o main func.o" - ok. If anybody,...

10. UNIX for Dummies Questions & Answers

Problem installing gcc

Hi! I have downloaded a precompiled gcc package but I'm having problems installing it. It is supposed to install in /usr/local and there is plenty of space left there but during the installation I get the following error message �No space left on device�. Is it some kind of temp folder that is out...

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)

Programming