DOCSLIB.ORG

Openvms Debugger Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Openvms Debugger Manual OpenVMS Debugger Manual Order Number: AA–QSBJD–TE April 2001 This manual explains the features of the OpenVMS Debugger for programmers in high-level languages and assembly language. Revision/Update Information: This manual supersedes the OpenVMS Debugger Manual, Version 7.2. Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, VAX, VMS, and the Compaq logo Registered in the U.S. Patent and Trademark Office. OpenVMS is a trademark of Compaq Information Technologies Group, L.P. in the United States and other countries. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States and other countries. Intel is a trademark of Intel Corporation in the United States and other countries. Motif, Open Software Foundation, OSF/1, and UNIX are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be the trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. ZK4538 The Compaq OpenVMS documentation set is available on CD-ROM. This document was prepared using DECdocument, Version 3.3-1b. Contents Preface ............................................................ xxv Part I Introduction to the Debugger 1 Introduction to the Debugger 1.1 Overview of the Debugger ..................................... 1–1 1.1.1 Functional Features ....................................... 1–2 1.1.2 Convenience Features ..................................... 1–4 1.2 Preparing an Executable Image for Debugging ..................... 1–6 1.2.1 Compiling a Program for Debugging . ....................... 1–6 1.2.2 Linking a Program for Debugging ............................ 1–7 1.2.3 Controlling Debugger Activation with the LINK and RUN Commands ....................................................... 1–7 1.3 Debugging a Program with the Kept Debugger ..................... 1–8 1.3.1 Starting the Kept Debugger . ................................ 1–9 1.3.2 When Your Program Completes Execution ...................... 1–12 1.3.3 Rerunning the Same Program from the Kept Debugger ........... 1–12 1.3.4 Running Another Program from the Kept Debugger .............. 1–13 1.4 Interrupting Program Execution and Aborting Debugger Commands .... 1–13 1.5 Pausing and Resuming a Debugging Session....................... 1–13 1.6 Starting the Debugger by Running a Program ..................... 1–14 1.7 Starting the Debugger After Interrupting a Running Program . ....... 1–15 1.8 Ending a Debugging Session . ................................ 1–16 1.9 Debugging a Program on a Workstation Running DECwindows Motif .... 1–16 1.10 Debugging a Program from a PC Running the Debug Client . ....... 1–17 1.11 Debugging Detached Processes That Run with No CLI ............... 1–18 1.12 Debugger Command Summary . ................................ 1–18 1.12.1 Starting and Ending a Debugging Session ...................... 1–18 1.12.2 Controlling and Monitoring Program Execution . ............... 1–19 1.12.3 Examining and Manipulating Data ........................... 1–19 1.12.4 Controlling Type Selection and Radix . ....................... 1–20 1.12.5 Controlling Symbol Searches and Symbolization . ............... 1–20 1.12.6 Displaying Source Code . ................................ 1–21 1.12.7 Using Screen Mode ....................................... 1–21 1.12.8 Editing Source Code ...................................... 1–21 1.12.9 Defining Symbols ........................................ 1–22 1.12.10 Using Keypad Mode ...................................... 1–22 1.12.11 Using Command Procedures, Log Files, and Initialization Files ..... 1–22 1.12.12 Using Control Structures . ................................ 1–22 1.12.13 Debugging Multiprocess Programs ........................... 1–23 1.12.14 Additional Commands ..................................... 1–23 iii Part II Command Interface 2 Getting Started with the Debugger 2.1 Entering Debugger Commands and Accessing Online Help ........... 2–1 2.2 Displaying Source Code . .................................... 2–4 2.2.1 Noscreen Mode ........................................... 2–4 2.2.2 Screen Mode . ............................................ 2–5 2.3 Controlling and Monitoring Program Execution . ................... 2–6 2.3.1 Starting or Resuming Program Execution . ................... 2–6 2.3.2 Executing the Program by Step Unit .......................... 2–7 2.3.3 Determining Where Execution Is Paused ....................... 2–7 2.3.4 Suspending Program Execution with Breakpoints ................ 2–8 2.3.5 Tracing Program Execution with Tracepoints ................... 2–9 2.3.6 Monitoring Changes in Variables with Watchpoints ............... 2–10 2.4 Examining and Manipulating Program Data ....................... 2–11 2.4.1 Displaying the Value of a Variable ............................ 2–12 2.4.2 Assigning a Value to a Variable . ............................ 2–13 2.4.3 Evaluating Language Expressions ............................ 2–13 2.5 Controlling Access to Symbols in Your Program . ................... 2–14 2.5.1 Setting and Canceling Modules . ............................ 2–14 2.5.2 Resolving Symbol Ambiguities . ............................ 2–15 2.6 Sample Debugging Session . .................................... 2–15 3 Controlling and Monitoring Program Execution 3.1 Commands Used to Execute the Program ......................... 3–1 3.2 Executing the Program by Step Unit . ............................ 3–2 3.2.1 Changing the STEP Command Behavior ....................... 3–2 3.2.2 Stepping Into and Over Routines . ............................ 3–3 3.3 Suspending and Tracing Execution with Breakpoints and Tracepoints . 3–4 3.3.1 Setting Breakpoints or Tracepoints on Individual Program Locations . ............................................ 3–6 3.3.1.1 Specifying Symbolic Addresses ............................ 3–6 3.3.1.2 Specifying Locations in Memory ........................... 3–7 3.3.1.3 Obtaining and Symbolizing Memory Addresses ............... 3–8 3.3.2 Setting Breakpoints or Tracepoints on Lines or Instructions ........ 3–8 3.3.3 Setting Breakpoints on Emulated Instructions (Alpha Only) ........ 3–9 3.3.4 Controlling Debugger Action at Breakpoints or Tracepoints ........ 3–9 3.3.5 Setting Breakpoints or Tracepoints on Exceptions ................ 3–10 3.3.6 Setting Breakpoints or Tracepoints on Events .................. 3–10 3.3.7 Deactivating, Activating, and Canceling Breakpoints or Tracepoints ....................................................... 3–11 3.4 Monitoring Changes in Variables and Other Program Locations ........ 3–11 3.4.1 Deactivating, Activating, and Canceling Watchpoints . ........... 3–14 3.4.2 Watchpoint Options . .................................... 3–14 3.4.3 Watching Nonstatic Variables . ............................ 3–14 3.4.3.1 Execution Speed . .................................... 3–15 3.4.3.2 Setting a Watchpoint on a Nonstatic Variable ................ 3–15 3.4.3.3 Options for Watching Nonstatic Variables ................... 3–16 3.4.3.4 Setting Watchpoints in Installed Writable Shareable Images . 3–16 iv 4 Examining and Manipulating Program Data 4.1 General Concepts ............................................ 4–1 4.1.1 Accessing Variables While Debugging . ....................... 4–1 4.1.2 Using the EXAMINE Command ............................. 4–2 4.1.3 Using the DUMP Command . ................................ 4–3 4.1.4 Using the DEPOSIT Command .............................. 4–3 4.1.5 Address Expressions and Their Associated Types . ............... 4–4 4.1.6 Evaluating Language Expressions ............................ 4–5 4.1.6.1 Using Variables in Language Expressions ................... 4–6 4.1.6.2 Numeric Type Conversion by the Debugger . ............... 4–7 4.1.7 Address Expressions Compared to Language Expressions . ....... 4–8 4.1.8 Specifying the Current, Previous, and Next Entity ............... 4–9 4.1.9 Language Dependencies and the Current Language .............. 4–10 4.1.10 Specifying a Radix for Entering or Displaying Integer Data . ....... 4–11 4.1.11 Obtaining and Symbolizing Memory Addresses . ............... 4–13 4.2 Examining and Depositing into Variables . ....................... 4–15 4.2.1 Scalar Types ............................................. 4–15 4.2.2 ASCII String Types ....................................... 4–16 4.2.3 Array Types ............................................. 4–17 4.2.4 Record Types ............................................ 4–18 4.2.5 Pointer (Access) Types ..................................... 4–19 4.3 Examining and Depositing Instructions ........................... 4–20 4.3.1 Examining Instructions .................................... 4–20 4.3.2 Depositing Instructions
Load more

Recommended publications
  • Latest X64dbg Version Supports Non-English Languges Through a Generic Algorithm That May Or May Not Work Well in Your Language
    x64dbg Documentation Release 0.1 x64dbg Jul 05, 2021 Contents 1 Suggested reads 1 1.1 What is x64dbg?.............................................1 1.2 Introduction...............................................1 1.3 GUI manual............................................... 15 1.4 Commands................................................ 31 1.5 Developers................................................ 125 1.6 Licenses................................................. 261 2 Indices and tables 277 i ii CHAPTER 1 Suggested reads If you came here because someone told you to read the manual, start by reading all sections of the introduction. Contents: 1.1 What is x64dbg? This is a x64/x32 debugger that is currently in active development. The debugger (currently) has three parts: • DBG • GUI • Bridge DBG is the debugging part of the debugger. It handles debugging (using TitanEngine) and will provide data for the GUI. GUI is the graphical part of the debugger. It is built on top of Qt and it provides the user interaction. Bridge is the communication library for the DBG and GUI part (and maybe in the future more parts). The bridge can be used to work on new features, without having to update the code of the other parts. 1.2 Introduction This section explains the basics of x64dbg. Make sure to fully read this! Contents: 1 x64dbg Documentation, Release 0.1 1.2.1 Features This program is currently under active development. It supports many basic and advanced features to ease debugging on Windows. Basic features • Full-featured debugging of DLL and EXE files (TitanEngine Community Edition) • 32-bit and 64-bit Windows support from Windows XP to Windows 10 • Built-in assembler (XEDParse/Keystone/asmjit) • Fast disassembler (Zydis) • C-like expression parser • Logging • Notes • Memory map view • Modules and symbols view • Source code view • Thread view • Content-sensitive register view • Call stack view • SEH view • Handles, privileges and TCP connections enumeration.
    [Show full text]
  • Intel® Inspector 2020 Update 2 Release Notes Intel® Inspector 2020 Update 2 to Learn More About This Product, See
    Intel® Inspector 2020 Update 2 Release Notes 16 July 2020 Intel® Inspector 2020 Update 2 Customer Support For technical support, including answers to questions not addressed in this product, visit the technical support forum, FAQs, and other support information at: • https://software.intel.com/en-us/inspector/support/ • http://www.intel.com/software/products/support/ • https://software.intel.com/en-us/inspector Please remember to register your product at https://registrationcenter.intel.com/ by providing your email address. Registration entitles you to free technical support, product updates and upgrades for the duration of the support term. It also helps Intel recognize you as a valued customer in the support forum. NOTE: If your distributor provides technical support for this product, please contact them for support rather than Intel. Contents 1 Introduction 2 2 What’s New 3 3 System Requirements 3 4 Where to Find the Release 5 5 Installation Notes 5 6 Known Issues 7 7 Attributions 13 8 Legal Information 13 1 Introduction Intel® Inspector helps developers identify and resolve memory and threading correctness issues in their C, C++ and Fortran applications on Windows* and Linux*. Additionally, on Windows platforms, the tool allows the analysis of the unmanaged portion of mixed managed and unmanaged programs and identifies threading correctness issues in managed .NET C# applications. Intel Inspector is a dynamic error checking tool for developing multithreaded applications on Windows or Linux operating systems. Intel Inspector maximizes code quality and reliability by quickly detecting memory, threading, and source code security errors during the development cycle. You can also use the Intel Inspector to visualize and manage Static Analysis results created by Intel® compilers in various suite products.
    [Show full text]
  • Demarinis Kent Williams-King Di Jin Rodrigo Fonseca Vasileios P
    sysfilter: Automated System Call Filtering for Commodity Software Nicholas DeMarinis Kent Williams-King Di Jin Rodrigo Fonseca Vasileios P. Kemerlis Department of Computer Science Brown University Abstract This constant stream of additional functionality integrated Modern OSes provide a rich set of services to applications, into modern applications, i.e., feature creep, not only has primarily accessible via the system call API, to support the dire effects in terms of security and protection [1, 71], but ever growing functionality of contemporary software. How- also necessitates a rich set of OS services: applications need ever, despite the fact that applications require access to part of to interact with the OS kernel—and, primarily, they do so the system call API (to function properly), OS kernels allow via the system call (syscall) API [52]—in order to perform full and unrestricted use of the entire system call set. This not useful tasks, such as acquiring or releasing memory, spawning only violates the principle of least privilege, but also enables and terminating additional processes and execution threads, attackers to utilize extra OS services, after seizing control communicating with other programs on the same or remote of vulnerable applications, or escalate privileges further via hosts, interacting with the filesystem, and performing I/O and exploiting vulnerabilities in less-stressed kernel interfaces. process introspection. To tackle this problem, we present sysfilter: a binary Indicatively, at the time of writing, the Linux
    [Show full text]
  • Digital Equipment: Corporation, Maynard, Massachusetts 01754 Digital Equipment Cor1poration • Maynard
    TOPS .. 10 DOCUMENTATION DIRECTORY Order Number AA-0858C-TB April 1979 This document describes the manuals for the TOPS·10 Software Notebooks. This manual supersedes the TOPS·10 Documentation Directory, Order Number AA·0858B·TB. To order additional copies; of this document, contact the Software Distribution Center, Digital Equipment: Corporation, Maynard, Massachusetts 01754 digital equipment cor1poration • maynard. massachusetts First Printing, February, 1978 Upda ted, May, 1978 Updated, June, 1978 Updated, August, 1978 Revised, Nov~mber, 1978 Revised, April, 1979 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. Digital Equipment Corporation assumes no responsibility for the use or reliability of its software on equipment that is not supplied by DIGITAL and its affiliated companies. copyright©l979 by Digital Equipment Corporation The postage-prepaid READER'S COMMENTS form on the last page of this document requests the user's critical evaluation to assist us in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DIGITAL DECsystem-lO MASSBUS DEC DECSYSTEM-20 OMNIBUS PDP DEC tape OS/8 DECUS DIBOL PHA UNIBUS EDUSYSTEM RSTS COMPUTER LABS FLIP CHIP RSX COMTEX
    [Show full text]
  • KTS-A Memory Management Control User's Guide Digital Equipment Corporation • Maynard, Massachusetts
    --- KTS-A memory management control user's guide E K- KTOSA-U G-001 digital equipment corporation • maynard, massachusetts 1st Edition , July 1978 Copyright © 1978 by Digital Equipment Corporation The material in this manual is for informational purposes and is subject to change without notice. Digital Equipment Corporation assumes no responsibility for any errors which may appear in this manual. Printed in U.S.A. This document was set on DIGITAL's DECset-8000 com­ puterized typesetting system. The following are trademarks of Digital Equipment Corporation, Maynard, Massachusetts: DIGITAL D ECsystem-10 MASSBUS DEC DECSYSTEM-20 OMNIBUS POP DIBOL OS/8 DECUS EDUSYSTEM RSTS UNI BUS VAX RSX VMS IAS CONTENTS Page CHAPTER 1 INTRODUCTION 1 . 1 SCOPE OF MANUAL ..................................................................................................................... 1-1 1.2 GENERAL DESCRI PTION ............................................................................................................. 1-1 1 .3 KT8-A SPECIFICATION S.............................................................................................................. 1-3 1.4 RELATED DOCUMENTS ............................................................................................................... 1-4 1 .5 SOFTWARE ..................................................................................................................................... 1-5 1.5.1 Diagnostic .............................................................................................................................
    [Show full text]
  • Building Custom Applications on MMA9550L/MMA9551L By: Fengyi Li Applications Engineer
    Freescale Semiconductor Document Number: AN4129 Application Note Rev. 0, 01/2012 Building Custom Applications on MMA9550L/MMA9551L by: Fengyi Li Applications Engineer 1Introduction Contents 1 Introduction . 1 The Freescale MMA955xL Xtrinsic family of devices 2 Architecture . 2 are high-precision, intelligent accelerometers built on the 2.1 Top-level diagram . 2 2.2 Memory space. 3 Freescale ColdFire version 1 core. 3 Tools to build custom projects . 6 3.1 MMA955xL template . 6 The MMA955xL family’s microcontroller core enables 3.2 Sensor Toolbox kit. 29 the development of custom applications in the built-in 3.3 MMA955xL reference manuals . 33 4 Template contents . 34 FLASH memory. Programming and debugging tasks are 4.1 Custom applications on the Freescale platform . 34 supported by Freescale’s CodeWarrior Development 4.2 Define RAM memory for custom applications . 36 Studio for Microcontrollers (Eclipse based IDE). 4.3 Set the custom application run rate. 38 4.4 Access accelerometer data . 39 4.5 Gesture functions . 40 The MMA9550L/MMA9551L firmware platform is 4.6 Stream data to FIFO . 43 specifically designed to ease custom application 4.7 Stream events to FIFO . 46 integration. Building custom applications on the built-in 5 Summary . 48 firmware platform provides an organized and more code-efficient sensing system to monitor development tasks, which reduces the application development cycle. This document introduces the code architecture required for creating a custom application, the instructions for binding it with the Freescale firmware platform, and the available tools that support the custom application development on the MMA955xL family of devices. © 2012 Freescale Semiconductor, Inc.
    [Show full text]
  • On the Cognitive Prerequisites of Learning Computer Programming
    On the Cognitive Prerequisites of Learning Computer Programming Roy D. Pea D. Midian Kurland Technical Report No. 18 ON THE COGNITIVE PREREQUISITES OF LEARNING COMPUTER PROGRAMMING* Roy D. Pea and D. Midian Kurland Introduction Training in computer literacy of some form, much of which will consist of training in computer programming, is likely to involve $3 billion of the $14 billion to be spent on personal computers by 1986 (Harmon, 1983). Who will do the training? "hardware and software manu- facturers, management consultants, -retailers, independent computer instruction centers, corporations' in-house training programs, public and private schools and universities, and a variety of consultants1' (ibid.,- p. 27). To date, very little is known about what one needs to know in order to learn to program, and the ways in which edu- cators might provide optimal learning conditions. The ultimate suc- cess of these vast training programs in programming--especially toward the goal of providing a basic computer programming compe- tency for all individuals--will depend to a great degree on an ade- quate understanding of the developmental psychology of programming skills, a field currently in its infancy. In the absence of such a theory, training will continue, guided--or to express it more aptly, misguided--by the tacit Volk theories1' of programming development that until now have served as the underpinnings of programming instruction. Our paper begins to explore the complex agenda of issues, promise, and problems that building a developmental science of programming entails. Microcomputer Use in Schools The National Center for Education Statistics has recently released figures revealing that the use of micros in schools tripled from Fall 1980 to Spring 1983.
    [Show full text]
  • DIBOL for Beginners Order No
    DIBOL for Beginners Order No. AA-BI77 A-TK April 1984 Supersession: This is a new manual. Operating System: VAXNMS, CTS-300, RSTS/E, Professional, RSX-11 M-Plus, Micro/RSX, Professional CTS-300 Software Version: Applicable to all products containing DIBOL-83 . First Printing, April 1984 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by DIGITAL or its affiliated companies. The specifications and drawings, herein, are the property of Digital Equipment Corporation and shall not be reproduced or copied or used in whole or in part as the basis for the manufacture or sale of items without written permission. Copyright © 1984 by Digital Equipment Corporation. All Rights Reserved The following are trademarks of Digital Equipment Corporation: CTI BUS MASSBUS RSTS DEC PDP RSX DECmate P/OS Tool Kit DECsystem-10 PRO/BASIC UNIBUS DECSYSTEM-20 Professional VAX DECUS PRO/FMS VMS DECwriter PRO/RMS VT DIBOL PROSE Work Processor mamDOma Rainbow CONTENTS Page PREFACE ............................................................................................. v INTRODUCTION ...................................................................... Introduction-1 CHAPTER 1 COMMUNICATING WITH YOUR COMPUTER ........................ 1-1 CHAPTER 2 HOW DATA IS STORED ..................................................... 2-1 Accessing Stored Data............................................................. 2-2 CHAPTER 3 HOW DATA IS PROCESSED ............................................... 3-1 The Basic Data Processing Cycle.............................................
    [Show full text]
  • HP Powerpoint 2000 Dark Template
    OpenVMS Strategy and Futures OpenVMS Division, Hewlett-Packard © 2006 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Agenda • OpenVMS Today • OpenVMS Tomorrow • Integrity Update • Summary 2 20 October 2007 OpenVMS Today 3 20 October 2007 The OpenVMS Mission Statement The OpenVMS Division is committed to delivering the OpenVMS roadmaps on time and with outstanding quality. The capabilities that customers have come to rely on in OpenVMS - leadership clustering, high availability, excellent quality, exceptional security and “bullet-proof” operations - will continue to be delivered and enhanced by HP, ensuring product leadership now and in the future. 4 20 October 2007 OpenVMS Celebrating 29 years across 3 computer architectures • Differentiating product • Some key Customers attributes Vodafone Toys R Us − Availability: Disaster Tolerance Deutsche Borse Renault − Clustering: Scalable to 96 nodes, Ikea USPS up to 500 miles apart Verizon Wireless Fraport USAF Commerzbank − Security: System and Cluster Mayo Foundation Intel − Best TCO in class Indian Railways PKE − Strong Integration technology Korean Exchange HKJC Veterans Association Volvo • Core Markets • Market Profile − Finance: Capital Markets, Retail − #1 rated in Healthcare Banking, Wholesale Banking, − 90% of manufacturing of the world’s CPU − Telecommunications: Mobile chips Billing, SMS, Prepaid, HLR, Cable − 30%+ of mobile phones billed in the world & Satellite TV − Over 50% of the world’s SMS transactions − Healthcare:
    [Show full text]
  • 1. with Examples of Different Programming Languages Show How Programming Languages Are Organized Along the Given Rubrics: I
    AGBOOLA ABIOLA CSC302 17/SCI01/007 COMPUTER SCIENCE ASSIGNMENT ​ 1. With examples of different programming languages show how programming languages are organized along the given rubrics: i. Unstructured, structured, modular, object oriented, aspect oriented, activity oriented and event oriented programming requirement. ii. Based on domain requirements. iii. Based on requirements i and ii above. 2. Give brief preview of the evolution of programming languages in a chronological order. 3. Vividly distinguish between modular programming paradigm and object oriented programming paradigm. Answer 1i). UNSTRUCTURED LANGUAGE DEVELOPER DATE Assembly Language 1949 FORTRAN John Backus 1957 COBOL CODASYL, ANSI, ISO 1959 JOSS Cliff Shaw, RAND 1963 BASIC John G. Kemeny, Thomas E. Kurtz 1964 TELCOMP BBN 1965 MUMPS Neil Pappalardo 1966 FOCAL Richard Merrill, DEC 1968 STRUCTURED LANGUAGE DEVELOPER DATE ALGOL 58 Friedrich L. Bauer, and co. 1958 ALGOL 60 Backus, Bauer and co. 1960 ABC CWI 1980 Ada United States Department of Defence 1980 Accent R NIS 1980 Action! Optimized Systems Software 1983 Alef Phil Winterbottom 1992 DASL Sun Micro-systems Laboratories 1999-2003 MODULAR LANGUAGE DEVELOPER DATE ALGOL W Niklaus Wirth, Tony Hoare 1966 APL Larry Breed, Dick Lathwell and co. 1966 ALGOL 68 A. Van Wijngaarden and co. 1968 AMOS BASIC FranÇois Lionet anConstantin Stiropoulos 1990 Alice ML Saarland University 2000 Agda Ulf Norell;Catarina coquand(1.0) 2007 Arc Paul Graham, Robert Morris and co. 2008 Bosque Mark Marron 2019 OBJECT-ORIENTED LANGUAGE DEVELOPER DATE C* Thinking Machine 1987 Actor Charles Duff 1988 Aldor Thomas J. Watson Research Center 1990 Amiga E Wouter van Oortmerssen 1993 Action Script Macromedia 1998 BeanShell JCP 1999 AngelScript Andreas Jönsson 2003 Boo Rodrigo B.
    [Show full text]
  • Linkers and Loaders Do?
    Linkers & Loaders by John R. Levine Table of Contents 1 Table of Contents Chapter 0: Front Matter ........................................................ 1 Dedication .............................................................................................. 1 Introduction ............................................................................................ 1 Who is this book for? ......................................................................... 2 Chapter summaries ............................................................................. 3 The project ......................................................................................... 4 Acknowledgements ............................................................................ 5 Contact us ........................................................................................... 6 Chapter 1: Linking and Loading ........................................... 7 What do linkers and loaders do? ............................................................ 7 Address binding: a historical perspective .............................................. 7 Linking vs. loading .............................................................................. 10 Tw o-pass linking .............................................................................. 12 Object code libraries ........................................................................ 15 Relocation and code modification .................................................... 17 Compiler Drivers .................................................................................
    [Show full text]
  • VSI Openvms Linker Utility Manual
    VSI OpenVMS Linker Utility Manual Document Number: DO–DLKRRM–01A Publication Date: August 2019 This manual describes the OpenVMS Linker utility. The linker creates images containing binary code and data that run on OpenVMS x86-64, OpenVMS I64, OpenVMS Alpha, or OpenVMS VAX systems. These images are primarily executable images activated at the DCL command line. The linker also creates shareable images that can be called by executable or by other shareable images. Revision Update Information: This is a new manual. Operating System and Version: VSI OpenVMS x86-64 Version 9.0 VSI OpenVMS I64 Version 8.4-1H1 VSI OpenVMS Alpha 8.4-2L1 VMS Software, Inc., (VSI) Bolton, Massachusetts, USA Linker Utility Manual: Copyright © 2019 VMS Software, Inc. (VSI), Bolton, Massachusetts, USA Legal Notice Confidential computer software. Valid license from VSI required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for VSI products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. VSI shall not be liable for technical or editorial errors or omissions contained herein. HPE, HPE Integrity, HPE Alpha, and HPE Proliant are trademarks or registered trademarks of Hewlett Packard Enterprise. Intel, Itanium, and IA-64 are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
    [Show full text]