From: Kevin K. <kev...@ch...> - 2006-05-28 21:11:38
|
> I have just released at the usual location (ticalc.org) a special build of > TiEmu3. This build does not include the GDB debugger but a VTI-style one > (almost the same as TiEmu2 without the license issues). I should clarify that all the VTI-style debugging facilities are available in the GDB-enabled releases too. (They use the disassembler from GDB, which allows them to show label names and such, but otherwise the ASM-level debugging windows are identical to those in the no-GDB version.) In GDB-enabled releases, you get: * C-level debugging through the linked-in Insight GDB frontend * ASM-level debugging through the built-in TiEmu debugger * symbolic information from GDB in the VTI-style disassembly window * seamless integration between the C-level and ASM-level debuggers In no-GDB releases, you get: * ASM-level debugging through the built-in TiEmu debugger Note that it is possible to build no-GDB binaries from the full GDB-enabled tarballs, just configure with --disable-gdb. (If you're using my 20060524 snapshot, make sure to apply tiemu3-20060524-fix-disable-gdb.diff, this is fixed in SVN.) If you're packaging TiEmu for other people to use, I recommend always enabling GDB, it's very useful for C programmers and it doesn't get into the way for others. (This remark doesn't apply to the Win32 binary packages, where we're intentionally providing both GDB-enabled and no-GDB binaries.) Kevin Kofler |