On Fri, Mar 29, 2002 at 04:29:59PM +0100, Olivier Chapuis wrote:
> Hello,
>
> At present time the fvwm lib is used in a totally static way.
> Moreover, an external module should be compiled inside the fvwm
> source tree to take advantage of the libs.
>
> One way to overcome these is to "libtooliz
Olivier Chapuis <[EMAIL PROTECTED]> writes:
> On Sat, Mar 30, 2002 at 10:35:14AM -0500, Dan Espen wrote:
> > The reason I posted was to point out that you could get more
> > detailed data. Jason showed how to do that on Linux.
>
> Yes, /proc/$PID/maps gives some info but I need to write
> a scrip
; > > > I do not know a lot of things on memory management (any good
> > > > doc and better tool than top and free?).
> > > ...
> > > > So the difference is not big when you really use fvwm.
> > > >
> > > > So now the big question: should I finish the
).
> > ...
> > > So the difference is not big when you really use fvwm.
> > >
> > > So now the big question: should I finish the libtoolization of fvwm
> > > and commit the change?
> >
> > It doesn't seem to be buying us much.
> >
>
On Sat, Mar 30, 2002 at 01:53:26PM +0600, Dmitry Yu. Bolkhovityanov wrote:
> On Fri, 29 Mar 2002, Olivier Chapuis wrote:
>
> > - if shared is enabled (and the system support shared lib) fvwm
> > will build and install a sharable library libfvwm.so-version and
> > fvwm2 and the modules will be dyna
t; source tree to take advantage of the libs.
> ...
> > Any way
> > I do not know a lot of things on memory management (any good
> > doc and better tool than top and free?).
> ...
> > So the difference is not big when you really use fvwm.
> >
> > So now the b
On Fri, 29 Mar 2002, Olivier Chapuis wrote:
> - if shared is enabled (and the system support shared lib) fvwm
> will build and install a sharable library libfvwm.so-version and
> fvwm2 and the modules will be dynamically linked to this library.
> Of course the system must be able to perform the dy
> "DE" == Dan Espen <[EMAIL PROTECTED]> writes:
DE> If you have access to Solaris, you can get some nice information
DE> from "pmap".
In Linux, this info (and more, I think) is in /proc/$PID/maps
- J<
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list
things on memory management (any good
> doc and better tool than top and free?).
...
> So the difference is not big when you really use fvwm.
>
> So now the big question: should I finish the libtoolization of fvwm
> and commit the change?
It doesn't seem to be buying us much.
FvwmBacker:224 80 144 128 (96) | 332 168 164 144 (188)
REAL is SIZE - SHARE
Note: I use --enable-xft and a big part of the shared mem come from
Xft, around 500k for fvwm2 at startup.
---
So the difference is not big when you really use fvwm.
So now the big question: should I finish t
10 matches
Mail list logo