Abstract: Methods for minimizing starting run time of application software are presented. Application software may be divided into blocks or components. If divided into blocks, a block may include a block loader function for calling another block having an instruction otherwise not included. Application software is transmitted to a client, which may begin execution as the application software is being transmitted. The client may encounter a block loader function causing the server to transmit the block that includes the instruction. In response to receiving the transmission, the client runs the application software using the instruction. If the application software is divided into components, each component may be encapsulated by a handler. A component may be divided into sub-components. A function included in a sub-component may be dependent upon a function in another sub-component. If the function is called, then the function(s) dependent upon the called function are transmitted to the client.

Abstract: Configuration of a debugger that saves resources and debugs on a target system rather than from a host system. The target system stores a table with global variables and addresses, and a module table with system-wide functions and addresses. In response to a trigger, a debugger module is loaded from the host system and linked to the target system by causing the debugger module to exchange information with the tables. The debugger module uses the table to find a variable address and sets a pointer to the address. The debugger module provides the table with a local name and address of a variable local to the debugger module. The debugger module uses the module table to find an MT address of a function and sets a pointer to the MT address. The debugger module provides the module table with an MT address of a function local to the debugger module.

Abstract: Linking of a new or updated module to an operating system without affecting other modules, and without reboot or recompilation. A core module includes a table of locations of application program interfaces of other modules. A selected module is linked to the core module. Specifically, the module is initialized and provided with a pointer to the core module's table. The table is provided with an address of the APIs of the module. The other modules are unaffected by the linking because they are not provided with the address of the module. A reboot or recompilation of the operating system is unnecessary because the other modules are unaffected. Nevertheless, the other modules have access to the APIs of the module and to each others' APIs through the core module.