Remote (host/target) debugging makes use of features in Visual Studio 2005 and .Net 2003, according to Ardence. It includes a "debug agent" that resides on the target and provides a communications mechanism over Ethernet back to the host machine running the debugger.
Another debugging enhancement is the RTX Debugger Data Extension, said to provide increased visibility into the RTX real-time kernel's internal data structures through a set of extension commands accessible through WinDbg and the Visual Studio IDE (.NET 2003 and 2005). Ardence says these extension commands can obtain the state of RTX processes, threads, memory information, process handles, objects, and RTX subsystems, as well the RTX version.
RTX subsystem architectureIn addition to Windows XP/XPe, RTX now "fully" supports Windows Server 2003 in both shared and dedicated modes, Ardence says. In shared mode, the RTX Subsystem shares one processor with Windows. In dedicated mode, RTX runs on a dedicated processor unavailable to Windows. Both shared and dedicated modes were tested with Windows Server 2003 on a 4 dual core CPU system with hyper-threading disabled and 8 GB of RAM, according to the company.
"RTX 7.0 is the result of Ardence's continued commitment to its customers' complex systems and changing design needs," said Stephen Woodard, Senior VP of Global Operations. "No other Windows-based product provides what RTX does, and we will continue to add cutting-edge functionality and capabilities that deliver value to customers and strategic partners worldwide."
RTX version 7.0 is available now, according to Ardence. Existing customers with current maintenance contracts can download the new version
here. It is "strongly recommended" that existing RTX customers upgrade to V7.0, the company says says.
Related stories:
