{"id":116371,"date":"2024-06-05T21:39:49","date_gmt":"2024-06-05T19:39:49","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/google-opublikoval-gwpsan-instrument-dlya-vyyavleniya-oshibok-na-stadii-vypolneniya-prilozhenij"},"modified":"2024-06-05T21:39:49","modified_gmt":"2024-06-05T19:39:49","slug":"google-opublikoval-gwpsan-instrument-dlya-vyyavleniya-oshibok-na-stadii-vypolneniya-prilozhenij","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/google-opublikoval-gwpsan-instrument-dlya-vyyavleniya-oshibok-na-stadii-vypolneniya-prilozhenij","title":{"rendered":"Google has released GWPSan, a tool for detecting runtime errors in applications","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Google has published the source codes of the GWPSan toolkit, designed to detect runtime errors in applications compiled for x86-64 and ARM64 architectures. GWPSan is compiled as a shared library that links at application startup using LD_PRELOAD and utilizes available Linux kernel mechanisms for stopping (PERF_TYPE_BREAKPOINT) and process sampling for program analysis. The code is written in C++ and is distributed under the Apache 2.0 license. <\/p>\n
GWPSan is structured as a modular framework that supports the addition of modules implementing various error class detectors. GWPSan performs dynamic analysis triggered through signal handlers, allowing it to operate without modifying the application's executable code. For most detectors to work effectively, the application must be compiled with certain compiler flags that add necessary metadata. At least Clang 18 and Linux kernel 6.4 are required. <\/p>\n
Currently, three detectors are available: <\/p>\n
\n
UAR (Use-after-return) \u2014 detects errors caused by using an object on the stack after exiting the function where that object was defined. The protection is organized by intercepting entry and exit points for the function \u2014 upon entry, the stack is replaced with a copy for use during the function's execution, and upon exit, the old stack state is restored.\n
TSan (Thread Sanitizer) \u2014 identifies data races between threads, occurring when different concurrently executing threads can read or modify shared memory areas without using synchronization primitives. The protection is built using hardware breakpoints tied to shared memory areas. An activating handler temporarily pauses thread execution when accessing memory, and during this pause, it checks for any breakpoints triggered by another thread.\n
LMSan (Lightweight Memory Sanitizer) \u2014 detects the use of uninitialized data in memory. The detector is marked as experimental and is not recommended for use. <\/ul>\n
GWPSan analyzes the executable code of a program using the DynamoRIO framework to decode machine code into abstract ISA instructions, which are then executed using emulation. Periodic signals from a timer trigger a unified handler, which executes a specific portion of instructions for the analyzed thread with each call. If certain instructions are detected during execution, a specific problem detector for those instructions is launched; for example, a race condition detector is initiated for instructions that access memory. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"