Xref: utzoo comp.windows.x:37832 comp.unix.wizards:26063
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!olivea!uunet!aspect!bobj
From: bobj@aspect.UUCP (Bob Joyce)
Newsgroups: comp.windows.x,comp.unix.wizards
Subject: -g libs on System V
Keywords: System V, Motif
Message-ID: <10570@aspect.UUCP>
Date: 19 Jun 91 20:45:49 GMT
Followup-To: comp.windows.x
Organization: Aspect Telecommunications, San Jose, Ca
Lines: 29



I recently ported a Motif-based program from a Sun Sparc machine to a Motorola 
MPC 200 running System V.  In both cases the program contained a "-g" version
of the Motif library.  

Two things surprised me:

	(1) The executable size was ~6 Meg on the sparc, but ~13 Meg on the
	    MPC.

	(2) Starting up the executable on the MPC under gdb took about 
	    20 minutes!.  Reason - the process consumed more than
	    40 Megabytes of memory, thereby causing intense swapping.
	    On the sparc, gdb started up in less than a minute and consumed
	    only about 6 Megs.  The same problem occurs with sdb and on
	    another System V, Motorola platform.

Is this problem common to System V architectures?  Is it particular to 
Motorola?  Have other Motif developers experienced high memory consumption
when they compile with "-g"?   Do developers have to be very selective
about their use of "-g"?

Thanks for any information.

					
					Bob Joyce
					uunet!aspect!bobj
					(408) 441-2236