![]() Installing a page fault handler is usually more efficient than doingĪccess checks in software at every access, because it's effectively the This library helps in implementing the others. Pageable virtual memory is usually done in the operating system's kernel. ![]() The list of platforms where this library is known to work is contained in Not defined, they will simply always return an error code or do nothing. On platforms where HAVE_SIGSEGV_RECOVERY or HAVE_STACK_OVERFLOW_RECOVERY is ![]() Note that the declared functions are available in all cases HAVE_STACK_OVERFLOW_RECOVERY will be defined if stack overflow handlersĪre available. Local SIGSEGV handlers are available, and the preprocessor macro Preprocessor macro HAVE_SIGSEGV_RECOVERY will be defined if global and Some platforms don't support this functionality. Stack overflow handlers: see tests/stackoverflow1.c.Local SIGSEGV handlers: see tests/sigsegv2.c.Global SIGSEGV handlers: see tests/sigsegv1.c.Stack overflow handlers: stackoverflow_install_handler, stackoverflow_deinstall_handler.Įach of the three APIs can be used independently or simultaneously.įor examples of the use of the APIs, see: Local SIGSEGV handlers (a handler per memory area): sigsegv_init, sigsegv_register, sigsegv_unregister, sigsegv_dispatch. Global SIGSEGV handlers: sigsegv_install_handler, sigsegv_deinstall_handler. This library supports three sets of functions, all defined in : memory-mapped access to persistent databases,.Catching and handling a page fault is a useful Occurs when a program tries to access to a region of memory that isĬurrently not available. GNU libsigsegv is a library for handling page faults in user mode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |