http://www.emilmont.net/ 2010-09-10T13:42:51-04:00 http://www.emilmont.net/ http://www.emilmont.net/lib/images/favicon.ico text/html 2010-09-09T06:56:05-04:00 Emilio Monti http://www.emilmont.net/doku.php?id=tools:code_coverage&rev=1284029765&do=diff Makefile: CC_FLAGS = -gdwarf-2 -static -fprofile-arcs -ftest-coverage LD_LIBS = -lgcov For each file: * At compile time a .gcno file is generated. It contains information to reconstruct the basic block graphs and assign source line numbers to blocks. * At run tine a .gcda file is generated. It contains arc transition counts, and some summary information. text/html 2010-09-07T10:47:43-04:00 Emilio Monti http://www.emilmont.net/doku.php?id=tools:function_call_trace&rev=1283870863&do=diff Notes about the article: Visualize function calls with Graphviz Basically the two fundamental changes for an instrumented application are: * compile each module to be tracked with: -gdwarf-2 -O0 -finstrument-functions * link the executable with the following module text/html 2010-09-05T08:10:29-04:00 Emilio Monti http://www.emilmont.net/doku.php?id=tools:dwarf&rev=1283688629&do=diff Documents: * Executable and Linking Format (ELF) Specification * DWARF 2.0 * Introduction to the DWARF Debugging Format * DWARF 2 Debugging Information Code: * libdwarf * python devtools.dwarf * debug_line Reader in Java GCC Produce debugging information in DWARF format (if that is supported). This is the format used by DBX on IRIX 6. Note that with DWARF version 2 some ports require, and will always use, some non-conflicting DWARF 3 extensions in the unwind tables. -gdwa… text/html 2010-09-02T06:11:24-04:00 Emilio Monti http://www.emilmont.net/doku.php?id=c:index&rev=1283422284&do=diff [C] Notes about the C: programming language, frameworks and libraries: c index External links: * C standard * Initialization * Programming in C * UNIX::interfaces&headers * Algorithms text/html 2010-08-24T11:31:31-04:00 Emilio Monti http://www.emilmont.net/doku.php?id=tools:gdb&rev=1282663891&do=diff * Howto: Porting the GNU Debugger * GDB internals * GDB Internals - A guide to the internals of the GNU debugger * ptrace * man Debug Session: Segmentation Fault How to get the stack trace of a program that causes a segmentation fault: gdb --args my_prog arg1 arg2 ... (gdb) run Program received signal SIGSEGV, Segmentation fault ... (gdb) backtrace text/html 2010-08-19T18:36:38-04:00 Emilio Monti http://www.emilmont.net/doku.php?id=embedded:os:rtos&rev=1282257398&do=diff * ChibiOS/RT * FreeRTOS * Atomthreads * FunkOS * SDPOS @see: List of real-time operating systems Embedded, OS, RealTime text/html 2010-08-16T09:53:42-04:00 Emilio Monti http://www.emilmont.net/doku.php?id=java:basic&rev=1281966822&do=diff Compile To compile a bunch of java files not organized in a package, for each file: javac -classpath . filename.java Launching Java Applications To launch the main static function of a {Class} inside a {package}, using the jar libraries (lib1.jar, lib2.jar) and a native library in the same directory.