Search Results for "memory"

Automation of Unit and System Tests. Tests can be implemented in any language and on many platforms. The flexible approach enables the inclusion of many types of tests, such as memory leak checks (using valgrind), coding rule checks, complexity checks, etc. Tests are run by a simple call to hwut in a base directory of a project. In particular for C, HWUT supports make file generation using 'sos' and 'sols' modes. Remote control-able function stubs may be generated using the 'stub' mode. Test cases can be generated using the 'gen' mode, and state machine walkers by the 'sm_walker' mode. ...

...The covered objects include packages, modules, functions, methods, scripts, and classes by two views: - File System View - packages, modules, and linenumbers - based on files and paths - Runtime Object View - callables, classes, and containers - based on in-memory RTTI / introspection The supported platforms are: - Linux, BSD, Unix, OS-X, Cygwin, and Windows - Python2, Python3 - CPython, PyPy Object addresses within modules - Object Identifier OID - and the display of the runtime call flow are supported by 'PyStackInfo'. Online documents: https://pysourceinfo.sourceforge.io/

.... - Easily debug memory-leaks. - Easily debug dangling pointers. - Easily debug deallocation method correctness. - Easily debug array index errors (when writing past the end). - Easily profile memory usage and track down memory hawks. - Click-And-Goto-Source support for Visual Studio. - Integrated compatibility for new, new[], delete, delete[], malloc, calloc, realloc, free

...SAR is cumulative activity counters in the operating system. It is the most comprehensive command which helps to monitor performance of various Linux / Solaris subsystems (CPU, Memory, I/O, Disk, Network, etc) all in same log. This makes it difficult to analyze since every counter data is dumped into the log file. SarBox helps to analyze this log file and present data in graphical charts or text format. To collect sar statistics from an environment, use below syntax [user@host ~]# sar -A 30 2 > sar_linux.log “30 2” reports for every 30 seconds and total of 2 times, written in sar_linux.log.

...The main advantages of minimock over other similar tools are its ease of use and its the low footprint : * executable is 20k large. (but on win$ it depends on cygwin1.dll that is 2Mb large) * avg memory use is 3/4Mb.

DUMA (Detect Unintended Memory Access) is a multi-platform memory debugging library. It can detect memory leaks and buffer overruns (or underruns) in a malloc() / new memory buffer. DUMA is a fork of Bruce Perens' Electric Fence library. sourceforge isn't maintained for many years! suggest you want to look at https://github.com/johnsonjh/duma