Sponsored Content
Full Discussion: Memory leaks on compilations
Homework and Emergencies Emergency UNIX and Linux Support Memory leaks on compilations Post 302459634 by teresaejunior on Tuesday 5th of October 2010 06:19:00 AM
Old 10-05-2010
Hello! Here are some details.

Code:
$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.4.5-2'
--with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++
--prefix=/usr --program-suffix=-4.4 --enable-shared --enable-multiarch
--enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.4 --libdir=/usr/lib --enable-nls
--enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
--enable-targets=all --with-arch-32=i586 --with-tune=generic
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
--target=i486-linux-gnu
Thread model: posix
gcc version 4.4.5 (Debian 4.4.5-2)

Code:
uname -a
Linux localhost 2.6.35-grml #1 SMP PREEMPT Sat Sep 4 10:58:14 UTC 2010 i686 GNU/Linux

But I tried also with kernels 2.6.35-6.dmz.2-liquorix-686 and 2.6.32-5-686 from Debian

After talking to you I tried a couple of different things, including "ulimit -v NUMBER" and "ulimit -m NUMBER" before compiling, but these don't seem to be respected, but I got to kill it before it killed me, so the build log is attached. You will notice that right in the beginning of the build it goes mad.

This one also looks problematic, the BSD daemon doesn't look so evil:
Code:
         (__) 
         (oo) 
   /------\/ 
  / |    ||   
 *  /\---/\ 
    ~~   ~~   
...."Have you mooed today?"...

Any more information you might need, I'll be glad to give.

Best regards,
Teresa e Junior

I forgot to mention, I have done a dist-upgrade this morning, but still no results.

Last edited by teresaejunior; 10-05-2010 at 07:25 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

memory leaks

Hi!! Experts, Any ideas how to check for the memory leaks in a process during performance testing?? I dont use purify.. Any way of finding it out using default S/W in HP UX-11 Can U gimme pointers to site having good scripts/tutorials on performance testing?? Thanx in Advance.. :) (3 Replies)
Discussion started by: jyotipg
3 Replies

2. HP-UX

Memory leaks on HP-UX 11i

Hi folks, We are using following listed configurations for a particular application. HP-UX 11i Sun Java 2 SDK Standard Edition 1.4.1 (version shipped with WebLogic 8) Oracle 9i Release 2 (Oracle 9.2.0) BEA WebLogic Server 8.1 SP3 It seems a memory leak when we use above configurations.... (1 Reply)
Discussion started by: gimhan90
1 Replies

3. Programming

Tool for finding memory leaks

hi, i am a c++ programmer working on linux(redhat linux8.0) environment, i need to find out the memory leaks, so far i didn't used any tools, so what are the tools are available, and whic one is good to use. plz provide with a small example. (1 Reply)
Discussion started by: sarwan
1 Replies

4. UNIX for Advanced & Expert Users

strange problem with memory leaks

Hi Unix lovers, I am facing a strange problem about memory leak. One component of our product show memory leak at customer's end but not in development environment. The memory used by the exe goes on increasing at customer end but not in dev. customer has same m/c(HP unix 11i) , the same... (1 Reply)
Discussion started by: shriashishpatil
1 Replies

5. Shell Programming and Scripting

Find memory leaks shell script ???

Hi all, Has anyone out there a shell script to detect memory leaks on unix machines? And if so what way did they go about it .? (5 Replies)
Discussion started by: nano2
5 Replies

6. UNIX and Linux Applications

Looking for memory leaks freeware tools

Hello all Is there good free ware tools to check software memory leaks ? Some thing like purify on unix platforms sun/hp/linux Thanks (3 Replies)
Discussion started by: umen
3 Replies

7. Solaris

How to find Total and Free Physical Memory and Logical Memory in SOLARIS 9

Hi, Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:- 1. Total Physical Memory in the system(total RAM). 2. Available Physical Memory(i.e. RAM Usage) 3. Total (Logical) Memory in the system 4. Available (Logical) Memory. I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies

8. AIX

valgrind - pthread memory leaks on AIX

Hi all, I have written a small code just to invoke main and return immediately. When built with libpthread on AIX box, valgrind throws lots of memory leak errors. But when built without libpthread, no issues at all. Here is the sample run for your look. Any idea where I might be going wrong?... (3 Replies)
Discussion started by: visionofarun
3 Replies

9. Solaris

[DOUBT] Memory high in idle process on Solaris 10 (Memory Utilization > 90%)

Hi Experts, Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing. Why memory utilization on solaris always looks high? I have statement about memory on solaris, is this true: Memory in solaris is used for... (4 Replies)
Discussion started by: edydsuranta
4 Replies

10. Programming

Memory Leaks

Suppose I have a main() function with only one malloc statement allocating say some 1 gb memory. Also say my system has 1 gb of ram. main() { malloc(1gb) return(0) } The program above exits without freeing the memory. In this case will the 1 gb of heap memory be returned... (9 Replies)
Discussion started by: rupeshkp728
9 Replies
dpkg-architecture(1)						  dpkg utilities					      dpkg-architecture(1)

NAME
dpkg-architecture - set and determine the architecture for package building SYNOPSIS
dpkg-architecture [option...] [command] DESCRIPTION
dpkg-architecture does provide a facility to determine and set the build and host architecture for package building. The build architecture is always determined by an external call to dpkg(1), and can not be set at the command line. You can specify the host architecture by providing one or both of the options -a and -t. The default is determined by an external call to gcc(1), or the same as the build architecture if CC or gcc are both not available. One out of -a and -t is sufficient, the value of the other will be set to a usable default. Indeed, it is often better to only specify one, because dpkg-architecture will warn you if your choice does not match the default. COMMANDS
-l Print the environment variables, one each line, in the format VARIABLE=value. This is the default action. -edebian-architecture Check for equality of architecture. By default debian-architecture is compared against the current Debian architecture, being the host. This action will not expand the architecture wildcards. Command finishes with an exit status of 0 if matched, 1 if not matched. -iarchitecture-wildcard Check for identity of architecture by expanding architecture-wildcard as an architecture wildcard and comparing against the current Debian architecture. Command finishes with an exit status of 0 if matched, 1 if not matched. -qvariable-name Print the value of a single variable. -s Print an export command. This can be used to set the environment variables using eval. -u Print a similar command to -s but to unset all variables. -c command Execute a command in an environment which has all variables set to the determined value. -L Print a list of valid architecture names. -?, --help Show the usage message and exit. --version Show the version and exit. OPTIONS
-adebian-architecture Set the Debian architecture. -tgnu-system-type Set the GNU system type. -f Values set by existing environment variables with the same name as used by the scripts are honored (i.e. used by dpkg-architecture), except if this force flag is present. This allows the user to override a value even when the call to dpkg-architecture is buried in some other script (for example dpkg-buildpackage(1)). TERMS
build machine The machine the package is built on. host machine The machine the package is built for. Debian architecture The Debian architecture string, which specifies the binary tree in the FTP archive. Examples: i386, sparc, hurd-i386. architecture wildcard An architecture wildcard is a special architecture string that will match any real architecture being part of it. The general form is <kernel>-<cpu>. Examples: linux-any, any-i386, hurd-any. GNU system type An architecture specification string consisting of two parts separated by a dash: cpu and system. Examples: i386-linux-gnu, sparc-linux-gnu, i386-gnu, x86_64-netbsd. VARIABLES
The following variables are set by dpkg-architecture: DEB_BUILD_ARCH The Debian architecture of the build machine. DEB_BUILD_ARCH_OS The Debian system name of the build machine. DEB_BUILD_ARCH_CPU The Debian cpu name of the build machine. DEB_BUILD_ARCH_BITS The pointer size of the build machine (in bits). DEB_BUILD_ARCH_ENDIAN The endianness of the build machine (little / big). DEB_BUILD_GNU_CPU The CPU part of DEB_BUILD_GNU_TYPE. DEB_BUILD_GNU_SYSTEM The System part of DEB_BUILD_GNU_TYPE. DEB_BUILD_GNU_TYPE The GNU system type of the build machine. DEB_BUILD_MULTIARCH The clarified GNU system type of the build machine, used for filesystem paths. DEB_HOST_ARCH The Debian architecture of the host machine. DEB_HOST_ARCH_OS The Debian system name of the host machine. DEB_HOST_ARCH_CPU The Debian cpu name of the host machine. DEB_HOST_ARCH_BITS The pointer size of the host machine (in bits). DEB_HOST_ARCH_ENDIAN The endianness of the host machine (little / big). DEB_HOST_GNU_CPU The CPU part of DEB_HOST_GNU_TYPE. DEB_HOST_GNU_SYSTEM The System part of DEB_HOST_GNU_TYPE. DEB_HOST_GNU_TYPE The GNU system type of the host machine. DEB_HOST_MULTIARCH The clarified GNU system type of the host machine, used for filesystem paths. DEBIAN
/RULES The environment variables set by dpkg-architecture are passed to debian/rules as make variables (see make documentation). However, you should not rely on them, as this breaks manual invocation of the script. Instead, you should always initialize them using dpkg-architecture with the -q option. Here are some examples, which also show how you can improve the cross compilation support in your package: Retrieving the GNU system type and forwarding it to ./configure: DEB_BUILD_GNU_TYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) DEB_HOST_GNU_TYPE := $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) [...] configure --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE) Doing something only for a specific architecture: DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH) ifeq ($(DEB_HOST_ARCH),alpha) [...] endif or if you only need to check the CPU or OS type, use the DEB_HOST_ARCH_CPU or DEB_HOST_ARCH_OS variables. Note that you can also rely on an external Makefile snippet to properly set all the variables that dpkg-architecture can provide: include /usr/share/dpkg/architecture.mk ifeq ($(DEB_HOST_ARCH),alpha) [...] endif In any case, you should never use dpkg --print-architecture to get architecture information during a package build. BACKWARD COMPATIBILITY
The /usr/share/dpkg/architecture.mk Makefile snippet is provided by dpkg-dev since version 1.16.1. The DEB_*_ARCH_BITS and DEB_*_ARCH_ENDIAN variables were introduced in dpkg-dev 1.15.4. Using them in debian/rules thus requires a build- dependency on dpkg-dev (>= 1.15.4). The DEB_HOST_ARCH_CPU and DEB_HOST_ARCH_OS variables were introduced in dpkg-dev 1.13.2. The -e and -i options were only introduced in relatively recent versions of dpkg-architecture (since dpkg 1.13.13). EXAMPLES
dpkg-buildpackage accepts the -a option and passes it to dpkg-architecture. Other examples: CC=i386-gnu-gcc dpkg-architecture -c debian/rules build eval `dpkg-architecture -u` Check if an architecture is equal to the current architecture or a given one: dpkg-architecture -elinux-alpha dpkg-architecture -amips -elinux-mips Check if the current architecture or an architecture provided with -a are Linux systems: dpkg-architecture -ilinux-any dpkg-architecture -ai386 -ilinux-any FILES
All these files have to be present for dpkg-architecture to work. Their location can be overridden at runtime with the environment variable DPKG_DATADIR. /usr/share/dpkg/cputable Table of known CPU names and mapping to their GNU name. /usr/share/dpkg/ostable Table of known operating system names and mapping to their GNU name. /usr/share/dpkg/triplettable Mapping between Debian architecture triplets and Debian architecture names. SEE ALSO
dpkg-buildpackage(1), dpkg-cross(1). Debian Project 2012-01-20 dpkg-architecture(1)
All times are GMT -4. The time now is 05:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy