Re: .EXE -> .ASM -> .EXE

"randyhyde@xxxxxxxxxxxxx" <randyhyde@xxxxxxxxxxxxx> écrivait
news:1151438097.356171.127590@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:


santosh wrote:
are bad; you're
operating under a serious misconception here.

I think they've been "scarred" by seeing certain statically linked
C/C++ executables. When you ask for static linking, sometimes the
entire libc is linked with your program resulting in a 800 kB hello
world demo. Similarly heavy use of templates can blow up a C++
executable to a megabyte or more.

That won't change with what they're trying to do, though. If a library
routine calls code in another library routine, which calls code in
another library routine, ..., etc., then you wind up bringing all the
code into your application. This is particularly troublesome with OOP
code, where the VMT often references every method/function in the
class, even if the code doesn't actually use it. Of course, this is not
the fault of the library, but of the original class design and a
"LibScanner" program won't solve this problem.

Ass-hole, if you had a real knowledge about how the static
libs are organized, you would understand that this kind of
mess is not specific to OOP.

Also, though i am not sure, i think that Santosh is a FASM
user, not a RosAsm user, and, anyway, the real purpose of
the RosAsm LibScanner, is NOT to solve this problem, as long
as, when it will be finished,... we will STILL have the same
problem. But, as you do not understand a thing at anything,
Well...


Of course runtime linking solves the problem...

That makes the size of the executable smaller, and allows other apps to
share the library in memory, but fundamentally you've still got to have
all the code in memory when the app runs.

Ass-hole, if you had a real knowledge about how the Dynamic
Libraries work under Windows, you would also know that they
save significative amounts of Memory. But, as you do not
understand a thing at anything, Well...


Betov.

< http://rosasm.org >



.

Relevant Pages

  • SUMMARY: Solaris equivalent for slibclean and dump -Hv ?
    ... 1- I understand that I don't need an equivalent to slibclean since Solaris ... simply frees unreferenced memory pages. ... executables: pldd, dump, elfdump. ... > and displays the path searched for libraries and libraries ...
    (SunManagers)
  • Re: .EXE -> .ASM -> .EXE
    ... C/C++ executables. ... another library routine, ..., etc., then you wind up bringing all the ... all the code in memory when the app runs. ... Yes, but with shared libraries, only one copy of the code needs to ...
    (alt.lang.asm)
  • Re: How does a shared library work?
    ... >in memory only the first moment that a dependant package is run. ... There are two levels of sharing of libraries. ... sense that two binary executables load the same file from disk, ... Keep Europe free from software patents, ...
    (Debian-User)
  • Re: Shared library usage by the process
    ... The usual way for sharing a library involves deferring the linking until ... Some libraries are widely used, like libc and libm, and benefit well from ... to have the same function in each), or between all executables. ...
    (comp.unix.questions)
  • Re: Shared library usage by the process
    ... The usual way for sharing a library involves deferring the linking until ... Some libraries are widely used, like libc and libm, and benefit well from ... to have the same function in each), or between all executables. ...
    (comp.unix.programmer)