Civil Rights
Movements, leaders, victories and the continuing fight for equality.
Explore the people, places, events, achievements, struggles and stories that shaped our journey.
Movements, leaders, victories and the continuing fight for equality.
Innovation, patents, science, technology and world-changing contributions.
Pioneers, champions, Negro Leagues, records, activism and excellence.
Meet the people whose lives, choices and achievements shaped the journey.
Black towns, communities, institutions and places where history happened.
Moments that changed communities, movements, institutions and the nation.
Wilmington, North Carolina once had a thriving Black middle class and an elected interracial government. In 1898 white supremacists used violence to overthrow that government, kill Black residents and drive many others from the city.
MORE →Reflects the personal views, recollections, and perspective of the author, Mike Davis.
This is a personal recollection on the Move fire on May 13, 1985
This article needs more citations. (July 2015) |
| adb | |
|---|---|
| Original author | Stephen R. Bourne |
| Developer | AT&T Bell Laboratories |
| Release | January 1979 |
| Operating system | Unix and Unix-like |
| Type | Command |
The advanced[citation needed] debugger adb is a debugger that first appeared in Seventh Edition UNIX.[1] It is found on Solaris, HP-UX, SCO and Venix. It is the successor of a debugger called db.
The initial version was written by Stephen R. Bourne.[2]
ADB was provided with Solaris until Solaris 8 (2000), when it was replaced by the Modular Debugger (mdb) with Solaris 8 (2000) and the ADB command-line interface now is emulated by mdb when it is called as adb. Mdb has become open source with OpenSolaris.[3] The SunOS kernel debugger kadb that was introduced with SunOS 3.5 (1986) is a minor variant of adb.
Source: Wikipedia. Article content is retrieved live through the MediaWiki API.
The advanced debugger adb is a debugger that first appeared in Seventh Edition UNIX. It is found on Solaris, HP-UX, SCO and Venix. It is the successor of a debugger called db.
On-line Debugging Tool (ODT) is a family of several debugger programs developed for Digital Equipment Corporation (DEC) hardware. Various operating systems including OS/8, RT-11, RSX-11, and RSTS/E implement ODT, as did the firmware console of all of the LSI-11-family processors including the 11/03, 11/23/24, 11/53, 11/73, and 11/83/84. The debugger allows access to memory using octal addresses and data. Within the software systems, the debugger accesses the process's address space. DEC's line of PDP-11 processors do not implement virtual memory, from an operating system perspective, but instead work in a fixed address space, which is mapped into a unified view of the program's address space, using an Active Page Register (APR). An APR can map the program's RAM in increments of 4K 16-bit words, to a maximum of 32K. In other words, an APR can map 8 segments of RAM, each limited to 4K. Because of this structure, an APR is able to map a maximum of 32K 16-bit words in RAM. In the case of RSTS/E, this usually means that a Runtime System, or RTS, maps to the upper portion of the address space and a user program resides in the lower portion of the address space. The RTS provides code to support access to the Operating System, on behalf of the user program; the RTS itself stores any of its non-static data in the address space of the user program, because the RTS is typically read-only. The operating system loads a single copy of the RTS and this is mapped to any user program that requires that RTS. The APR is set to map the RTS into the upper portion of the program's address space, in 4 KiB increments. So the BASIC Plus RTS (for the Basic+ Programming Language) typically maps 16 KiB to itself and the user program is mapped, in 4 KiB increments, in the lower 16 KiB. The RT11 RTS occupies 4 KiB, so a user program, like the RT11-based Peripheral Interchange Program (PIP), can expand to a maximum of 28 KiB. ODT can be used to "patch" binary modules, like an RTS, without requiring the re-compilation of the binary's source. The firmware console implementation accesses physical memory. ODT is a non-symbolic debugger and implements similar functionality to Advanced Debugger (adb) on Unix systems.
The Jasik Debugger (or more correctly, The Debugger from Jasik Designs), was a debugger tool for the classic Mac OS. Pitched as a much more powerful alternative to Macsbug, it was a popular choice among professional Mac developers until the advent of more advanced source-level debuggers such as that built into Metrowerks Codewarrior. This debugger first appeared in the late 1980s and was usually referred as MacNosy. "MacNosy" because it had a built-in powerful code-path tracer and disassembler. One could point it at an entry point into the code and MacNosy would disassemble code from that point down and follow calls and jumps and disassemble those sections too. When it o go a computed jump, it could find the associated jump table and then disassemble from those pointed-to locations. The command syntax for doing this was a bit obscure, but it could be made to work. In this way one could disassemble large programs, such as the Turbo Pascal compiler. While Jasik's debugger featured a graphical user interface, it was laid out in a very arbitrary and peculiar way, with buttons seemingly randomly sized and positioned. This gave it a reputation as difficult to use.
A flash emulator or flash memory emulator is a tool that is used to temporarily replace flash memory or ROM chips in an embedded device for the purpose of debugging embedded software. Such tools contain Dual-ported RAM, one port of which is connected to a target system (i.e. system, that is being debugged), and second is connected to a host (i.e. PC, which runs debugger). This allows the programmer to change executable code while it is running, set break points, and use other advanced debugging techniques on an embedded system, where such operations would not be possible otherwise. This type of tool appeared in 1980s-1990s, when most embedded systems were using discrete ROM (or later flash memory) chip, containing executable code. This allowed for easy replacing of ROM/flash chip with emulator. Together with excellent productivity of this tool this had driven an almost universal use of it among embedded developers. Later, when most embedded systems started to include both processor and flash on a single chip for cost and IP protection reasons, thus making external flash emulator tool impossible, search for a replacement tool started. And as often happens when a direct replacement is being searched for, many replacement techniques contain words "flash emulation" in them, for example, TI's "Flash Emulation Tool" debugging interface (FET) for its MSP430 chips, or more generic in-circuit emulators, even though none of two above had anything to do with flash or emulation as it is. Flash emulator could also be retrofitted to an embedded system to facilitate reverse engineering. For example, that was main hardware instrument in reverse engineering Wii gaming console bootloader.
Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.
MORE →Mae Jemison, aboard Space Shuttle Endeavour in 1992.