Google Wave Client-Server Protocol reference implementation. This C# application is a working reference implementation of the Google Wave Client-Server Protocol. The accompanying Wiki describes the internal working of the reference implementation.
Hardware Memory Checker
This is a memory checker utility that provides memory allocation and release functionality. It uses the memory paging system to allocate a guard page after each page of memory to provide a hardware boundary that can detect memory overflows. This allows for immediate detection of buffer overflow error conditions. There are many other memory checker programs in existence - why do we need another? This Hardware Memory Checker provides a combination of features not found in other memory checkers. - it uses the hardware paging system for immediate error detection (most other memory checkers look for modified memory in no mans land) - it is very fast compared to other hardware memory checkers because it makes fewer changes to the paging tables - it can track the original release location when debugging duplicate free problems - it is designed for large scale integration with the ability to call user defined fail functions
LuaEdit is an IDE/Text Editor/Debugger for the Lua language. Its interface looks like MS Visual Studio .Net� and includes syntax highlighting, code completion, advance breakpoint management, efficient search engines, etc. Client under GPL and server (core debugger) under LGPL.
Simulate on PC MSC51 microcontroler application by assembler opcode interpretation. Have interface to custom peripheric and memory organization. Enable to dump and modify memory and registers.
MinGW GCC cross development environment for ARM.
This is a Windows command line based cross development environment for ARM built from the latest stable release of GCC (currently 5.2.0) and includes global loop optimization support. Also included are Gnu make and gdb along with the necessary MinGW dlls to make it all work. Unzip the archive to the location of your choice, include the top level "bin" directory in your path and start developing.
MinGW GCC cross development environment for M68K.
This is a Windows command line based cross development environment for the M68K family of processors built from the latest stable release of GCC (currently 5.2.0) and includes global loop optimization support. Also included are Gnu make and gdb along with the necessary MinGW dlls to make it all work. Unzip the archive to the location of your choice, include the top level "bin" directory in your path and start developing.
MinGW GCC cross development environment for Power PC.
This is a Windows command line based cross development environment for Power PC built from the latest stable release of GCC (currently 5.2.0) and includes global loop optimization support. Also included are Gnu make and gdb along with the necessary MinGW dlls to make it all work. Unzip the archive to the location of your choice, include the top level "bin" directory in your path and start developing.
object orientated scripting language
ObjectiveScript is an object orientated scripting language that tries to combine the speed of scripting with an object orientated syntax similar to Java and C++. The language offers native data types like bool, double, float, int and string as well as user defined object types and a system library with data types similar to the Java boxed types like Integer and String. Collections like List, Map, etc. can be used with object and value types and can also be used as raw types (i.e. List == List<Object>).
Testing tool for Semantic Bridges. Supports the evaluation of rule-based (SWRL) ontology mappings to provide trust in a distributed multi-actor environment with heterogeneous independent information models materialized in OWL ontologies. See QualiPSo.org
This is a port of several development tools for Freescale M68HC08/HCS08 embedded microcontrollers families. Currently work is focused on binutils (as,ld), gdb and sim port. GCC, newlib, etc. porting will start after finishing the main as/ld support.
FreePascal based debugger and freepascal debugger lib. An alternative for C-based gdb.
JTAG interface library for FTDI chips. Linux port of the ftcjtag library from ftdi( http://bit.ly/98Vul3 ). Implementation relies on ftd2xx.so ( not libftdi.so ) which makes it windows compatible.
A library for monitoring the garbage collection of app objects
gcRadar is not a static code anayser but it is a library using which is ment to beused in your source code and it will monitor and report the lifetime events of yuor objects. gcRadar can provide this information by using callbacks, log4j & polling. gcRadar can monitor entities ranging from individula objects to full object trees comprising of is-a & has-a relationships. By using gcRadar you can monitor the lifetime of the objects that are created by your application in runtime, gcRadar enables the application to be aware of the memory constaraints that arise at runtime. The workings of the mythical Java Garbage Collector have for long eluded the common developer. Now by gcRadar enable you to record the life and death of objects at runtime.
latrace is frontend for the glibc 2.4+ LD_AUDIT feature
C++ exception (and generic) stack trace library (now libinstrument)
Project is migrating to libinstrument (https://sourceforge.net/projects/libinstrument/) Libcsdbg is a C++ exception stack tracer, offers the tools to create and process exception traces, the path an exception has propagated up the call stack, unwinding it, up to the point where it was handled. The traces are detailed with demangled function signatures and addr2line info (source file and line of each function call). Libcsdbg will perform flawlessly with multi-threaded programs, with dynamically linked shared objects (DSO) and with any statically linked library. Libcsdbg helps the developer/tester also create stack traces of any thread, at any point during, as a snapshot of the runtime call graph. This is very useful in cases of fatal errors, reception of terminating signals or process abortion/termination (such as segmentation faults)
Bit level lambda continuations and nothing else - Queue automata
Not working yet. To deal with the Halting Problem, computing and data are navigated using debugger ops: linearForward and treeForward, which navigate an astronomically large bit string where 1 is ( and 0 is ). All pairs are derived from (). For example, true is represented as ((()())()), and false is (()(()())). It appears related to the church encoding of lambda where T chooses first parameter and F chooses second, of a pair. Continuations are nearly finished code and are represented as a pair of stack and queue. The stack is a linked list of pair of true or false and object pushed on the stack. The queue is also such a linked list but is paired oppositely so previous queue state goes on the left and next object queued on the right of the new pair, so when the queue is navigated in sequence of that astronomically long bitstring (thats exponential of reusing objects in the acyclicNet), the Nav32 (using linearForward and treeForward for random access) first sees the oldest object queued