- Differences
between OSS and Symbian GLib
- GLib
Event Loop
The GLib event loop manages all the sources of an event available
for GLib. These events can come from different kinds of sources like file
descriptors (plain file descriptors, sockets, or pipes), time-outs, or any
kind of source that can be added.
- Introduction
to libgmodule
libgmodule has APIs that provide a portable method
for dynamically loading 'plug-ins' or, in other words, DLLs. Any program that
wants to dynamically load modules must be linked to libgmodule.
- Introduction
to GLib Low Memory Handler
The default behavior of GLib in Linux is such that in case of a
memory allocation failure, the GLib memory allocation API will call abort
and hence terminate the application.
- UHEAP
Markers and Panics in GLib-based Applications
The 2.10.x version of GLib has introduced a new type of memory
allocator called slice allocator. These allocators allocate memory in page
sizes even for a small request of something like 20 bytes. Once a huge chunk
has been allocated, all the future memory requests are granted using the chunk
that was allocated for the first memory request. Once the free pool runs out,
another huge chunk is allocated.