Skip to main content

Dynamic linking and static linking

*   A dynamicllay linked executable is smaller than its statically
counterpart. It saves disk and virtual memory, as libraries
are only mapped in to the process when needed.

* All executables dynamically linked to a particular library share
a single copy of the library at runtime. The kernel ensures that
libraries mapped into memory are shared by all processes using
them. This provides better I/O and swap space utilization and
in sparing of physical memory, improving overall system throughput.

* Dynamic linking permits easy versioning of libraries. New libraries
can be shipped; once installed on the system, old programs
automatically get the benefit of the new version without needing
to be relinked.

* Finally (much less common), dynamically linking allows users to
select at runtime which library to execute against. It's possible
to create library versions that are tuned for speed, or for
memory efficiency, or that contains extra debugging information,
and allow the user to express a preference when execution takes
place by substituting one library file for another.

Comments

Popular posts from this blog

Dotnet, .Net 3.5, 2.0, C# Interview Questions

Few questions on dotnet, C# 2.0, 3.5 On Object oriented concepts 1)What is inheritance with e.g 2)What is polymorphism -function overloading -Function overriding -virtual keyword use -Static keyword and use -Abstract classes -Interface -Object 3)What is threading and how do we use in realtime application(cognizant) 4)What is threadpooling, lock, monitor(write code sample) 5)Architecture of current project 6)Session state, diffrent types of state management. 7)What is Application_Start, how it works. 8)Type of authentication in asp.net 9)How to configure ASP.NET application. 10) What is Impersonation. 11) What is WebService, WSDL, UDDI, Discovery, asmx files. 12) How to implement WebService and use it. 13) When to use WebServices. 14) WPF, how to implement(BOA) 15) Testing concvepts. 16) Test attributes 17) Flow of Automation Test Method execution 18) Features of dotnet 3.5 19) CLR, garbage collection 20) Finally block 21) Manifest, Metadata, MSIL 22) Assemblies, Type of assemblies, str...

Remote debugging for ARM target board

Remote debugging for ARM target board With GDB one can both trace and modify code and data flow, and otherwise analyze the behavior of code, without explicitly changing any of it. Rather than run a full-blown instance of GDB on the target platform, you can use GDBserver , a program that lets you run GDB on a different machine than the one on which your program is running. The advantage of using GDBserver is that it needs just a fraction of the target resources that GDB consumes, because it implements only the low-level functionality of the debugger -- namely setting breakpoints and accessing the target processor registers and read/write application memory. GDBserver takes control of the application being debugged, and then waits for instructions from a remote instance of GDB running on a development workstation. Remote target needs to have debugging stub (gdbserver), The gdbserver is also referred to as the 'stub' and must be cross-compiled for that targ...