Classic Mac OS Software (Discussions on Applications) > Hacking the System, Mac OS 9.3, and Beyond !


(1/4) > >>


--- Quote ---MacsBug is a low-level (assembly language/machine-level) debugger for the classic Mac OS (Macintosh operating system). MacsBug is an acronym for Motorola Advanced Computer Systems Debugger, as opposed to Macintosh debugger (The Motorola 68000 Microprocessor is imprinted with the MACSS acronym[1]). The original version was developed by Motorola as a general debugger for its 68000 systems — it was ported to the Mac as a programmer's tool early in the project's development.

MacsBug is invoked by hitting the Macintosh's "Programmer's Key" or, as it became later known, the "Interrupt Key" or by pressing "Command-Power". MacsBug offers many commands for disassembling, searching, and viewing data as well as control over processor registers. MacsBug is not installed by default with Mac OS, although every Macintosh since the Macintosh Plus includes a debugger in ROM known as MicroBug.[2]

Users who stumble into MacsBug by accident need only to enter G and press return to escape from MacsBug; however, MacsBug is not installed by default, requiring a system extension, so a typical user environment does not include it. However, it was occasionally installed by end users to provide very basic error recovery. As the classic Mac OS lacked memory protection, "hard crashes" where an application crash simply froze the entire system weren't uncommon. With MacsBug installed, instead of an unresponsive system, the user would be dumped into MacsBug, where they could type ES to Exit to Shell (force quit the crashed application and return to the Finder) or RB for ReBoot, which restarted the system.[3] Such recovery efforts were often not successful, with the only alternative a hard reset.

In Mac OS versions 7.5 and later, the presence of MacsBug is indicated at startup; it is present if the user sees the text Debugger installed (although, occasionally, this may indicate the presence of another piece of software loaded into the area of memory reserved for the debugger, instead).

MacsBug was originally for the Motorola 68000 series of processors only. When Apple introduced the Power Macintosh in 1994, it was followed by an updated MacsBug that supported the PowerPC instruction set and architecture.

The last version of MacsBug was 6.6.3, released September 14, 2000. This final version works with all of the machines released in the July–September timeframe of 2000, including the Power Mac G4 (uni- and multi-processor), Power Mac G4 Cube, the iMac family (Ruby, Indigo, Sage, Graphite, and Snow), and the iBook family (Indigo, Key Lime, and Graphite).

6.6.3 includes better support for debugging MP tasks, and fixes some serious bugs in the memory setting commands when used in PCI I/O space. It can also be used in Classic when running under Mac OS X, where it is invoked by pressing "⌘-⏏" (or "⌘-F12" on systems without an Eject key).

Mac OS X allows programmers to use familiar MacsBug commands in gdb. This gdb plugin is included with the OS X Developer Tools, located in the directory /usr/libexec/gdb/plugins/MacsBug/.

Third party alternatives to MacsBug included ICOM Simulations' TMON which came with the Darin Adler Extended User Area & Trap Discipline (allowing all documented Mac API parameters to be verified) and the fully symbolic Jasik debugger, which was much more powerful, but harder to use due to the intricate and non-standard user interface.
--- End quote ---,TMON/index.html

Garden to rescue, again


--- Quote from: Protools5LEGuy on November 16, 2016, 08:01:20 PM ---
Garden to rescue, again

--- End quote ---

ProTools, please don't hotlink to the garden. You can link to the MacBugs page, but please don't hotlink directly to the downloadable file.

You can hotlink to macintosharchive if you want, I have nothing to do with that site :P

Ok. Hotlinks removed

Anyone found the MP (Multiprocessing) dcmd? It'd help with the NK work.


[0] Message Index

[#] Next page

Go to full version