DOCSLIB.ORG

New Architectures Support for ALMA Common Software: Lessons Learned

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
New Architectures Support for ALMA Common Software: Lessons Learned New Architectures Support for ALMA Common Software: Lessons learned Camilo E. Menaya, Gabriel A. Zamoraa, Rodrigo J. Tobarb, Jorge A. Avariasc, Kevin R. Dahl-Skoga, Horst H. von Branda and Gianluca Chiozzib a Computer Systems Research Group, UTFSM, Valpara´ıso, Chile; b European Southern Observatory, Garching bei Munc¨ hen, Germany; c National Radio Astronomy Observatory, Socorro, NM, USA ABSTRACT ALMA Common Software (ACS) is a distributed control framework based on CORBA that provides communi- cation between distributed pieces of software. Because of its size and complexity it provides its own compilation system, a mix of several technologies. The current ACS compilation process depends on specific tools, compilers, code generation, and a strict dependency model induced by the large number of software components. This doc- ument presents a summary of several porting and compatibility attempts at using ACS on platforms other than the officially supported one. A porting of ACS to the Microsoft Windows Platform and to the ARM processor architecture were attempted, with different grades of success. Also, support for LINUX-PREEMPT (a set of real-time patches for the Linux kernel) using a new design for real-time services was implemented. These efforts were integrated with the ACS building and compilation system, while others were included in its design. Lessons learned in this process are presented, and a general approach is extracted from them. Keywords: ALMA, ACS, CORBA, framework porting, multi-platform 1. INTRODUCTION The creation of full cross-platform compatible code is not trivial, even when this is a problem that has been studied before. The complexity is high, and it is even worse when the framework itself does not consist in a few set of files, but of a large amount of code written in several languages, lot of scripts, building patterns, testing tools, code generations, and much more. The work presented in this document is focused on such a framework: ALMA Common Software (ACS). ACS is a distributed control framework based on CORBA intended to be used as a standard for all the software and subsystems that conform the ALMA project.1, 2 Thanks to its open LGPL license, ACS can be used in any other astronomical project, particle accelerators and also allows the contributions of many users and researchers, thus making it possible to change the source code if needed for specific needs. The official release of ACS is only supported on Scientific Linux and Red Hat Enterprise Linux. This limitation can be a disadvantage when thinking on using ACS for other projects, as all the tool development environments and expected hardware are limited to the the ones supported by the mentioned operating system flavors. Since the first releases of ACS, several efforts have been made to open it to new platforms and architectures, but due to different constraints this has not been always an easy task. From the most important strict limitations with some base tools software versions (i.e.: GCC and glibc), to the small or non existent support on other completely different architectures, like embedded systems or the widely used Microsoft Windows. Since ACS has always been focused to a few Linux distributions, and also because all of the development and changes made in the meantime, this relation is now stronger, making it harder to break. As explained in the following sections, ACS is built on several base operating system tools, and some of its external products have low level communication with the underlying platforms, making the task of porting ACS to a non-officially architecture or platform non trivial . These constraints and difficulties have been addressed by the ALMA-UTFSM Group during a long timespan, which has generated a large amount of knowledge and experience on how we can extend a large complex framework such as ACS to new uses. It is also important for frameworks like ACS, and projects like ALMA, which have a long expected life-time, must be constantly adapting to technology changes; otherwise, they will become quickly obsolete, or will become increasingly hard to support. In this document we want to share the lessons, experiences and conclusions that we have acquired during this work. These have been (and will be) important to achieve the objective of adding support to new architectures and platforms, not limited to ACS, but also to any other large software framework. 1.1 The ALMA Common Software ALMA3 is a radio-astronomy project conducted by the European Southern Observatory (ESO), the National Astronomical Observatory of Japan (NAOJ) and the National Radio Astronomy Observatory (NRAO). It will consist in 66 antennas, located on the Chajnantor plateau (in the North of Chile), that will be used simultaneously to make radio-interferometry, being able to observe and study phenomena never studied before. This project implies a large number of challenges, starting from the geographic location: antennas will located at 5000 [m] above sea level, while the Operations Support Facility (OSF) is being based at an altitude of 2800 [m]. This is the place where main operations are carried out, and people will not be present frequently at the high site. To cover the distributed nature of the problem, ALMA Common Software2 (ACS) has been developed. ACS is a distributed control framework developed to be used not only by ALMA, but also by any other project that might want to use it. ACS is based on CORBA technology, and includes open-source ORB implementations for C++, Java and Python (TAO,4 JacORB5 and OmniORB6 respectively). It is distributed under the LGPL license, allowing it to be used in other projects, and facilitating its development by including people outside the project. Apart from being based on CORBA, ACS uses the Container/Component architecture for software devel- opment/deployment. Developers write Components, which in turn are run in Containers. Containers can run on different hosts, and are available for the three mentioned programming languages. The entire set of running containers that conform a given deployment is orchestrated by a Manager. There are also other services and facilities, such as a centralized Configuration DataBase (CDB), Logging Service, Alarm Service, Notification Channels, and more. ACS provides a standard environment which must be loaded for getting access to all its components. When developing under ACS, this environment also provides a set of Makefiles, which are the main actors in the ACS building system. This environment is heavily based on UNIX tools, and currently ACS is only officially supported on Red Hat Enterprise Linux and some versions of VxWorks. 2. WORK DESCRIPTIONS The following is an explanation of the development of different tasks performed in this work, detailing method- ologies, tools and techniques used, in addition to pointing out the disadvantages and degrees of success in these tasks 2.1 Porting ACS to different Linux distributions and newer GNU compiler versions A first attempt to port ACS to a different Linux distribution was done back then when ACS version 3 was released (2003). This effort was done by the Observatorio Astron´omico Nacional (OAN), Spain∗. The porting was done using Debian 3 as Linux distribution, which is quite different from Red Hat Linux. The main problems were the compatibility of the GNU C compiler (GCC) suite used in Debian (version 2.95). In contrast, Red Hat Linux 7.2 (the supported platform for ACS at that time) used GCC 2.96. This version of GCC was an experimental branch, a pre-release of GCC 3. The two GCC versions generated incompatible binaries and the code gave strange errors when compilation was tried on Debian 3. When ACS 4 was released (2005), it used GCC 3.2 for building. This time the compatibility between ACS 4 and Debian 3.1 was very straightforward, because the binaries were compatible between Red Hat Linux 8, the Linux distribution supported at this time, and Debian 3.1. To use ACS it was only required to install the binary files directly, fix a couple of symbolic links and set the environment variables needed by ACS properly. This situation was maintained until ACS 5 (2006). ∗http://almasw.hq.eso.org/almasw/bin/view/ACS/PortingAcsToDebian By the time of the ACS 6 (2007) release, the computers’ hardware had changed, sometimes incompatible with the Linux distributions that ACS supported. For ACS to run on new hardware, it was necessary to use a newer Linux distribution built with the GCC 4 compiler, or port the needed drivers to the kernel used by the official supported distribution. This task was not always possible, and, as had happened before, GCC 3 generated binaries incompatible with GCC 4. Therefore, this time it was necessary to port the entire ACS code to the new compiler. The ALMA-UTFSM Group7 had previously done a successful ACS porting from Red Hat Enterprise Linux (RHEL) 4 to Fedora Core 6 (base for RHEL 5).8 During this task the major problem was the change of the C++ compiler from one distribution to another: RHEL 4 uses GCC suite version 3.4, while Fedora Core 6 used GCC version 4.1. This version difference caused that the source code of ACS could not be built directly, basically because the newer version of GCC is more strict with the syntax and handling static global variables. This new compiler version also added new features which were, in some cases, incompatible with the source code of ACS written for GCC 3.4. Thanks to the work done by the ALMA-UTFSM Group, ACS now can be used on different Linux distributions that use newer GCC versions. Currently, ACS runs on Ubuntu Linux 7.10, 8.04, 8.10; Debian Linux, OpenSuse Linux 10 and 11.
Load more

Recommended publications
  • The GNU Configure and Build System
    The GNU configure and build system Ian Lance Taylor Copyright c 1998 Cygnus Solutions Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the con- ditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another lan- guage, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. i Table of Contents 1 Introduction ............................... 1 1.1 Goals................................................... 1 1.2 Tools ................................................... 1 1.3 History ................................................. 1 1.4 Building ................................................ 2 2 Getting Started............................ 3 2.1 Write configure.in ....................................... 4 2.2 Write Makefile.am ....................................... 6 2.3 Write acconfig.h......................................... 7 2.4 Generate files ........................................... 8 2.5 Example................................................ 8 2.5.1 First Try....................................... 9 2.5.2 Second Try.................................... 10 2.5.3 Third
    [Show full text]
  • Cygwin User's Guide
    Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 .
    [Show full text]
  • Integrating the GNU Debugger with Cycle Accurate Models a Case Study Using a Verilator Systemc Model of the Openrisc 1000
    Integrating the GNU Debugger with Cycle Accurate Models A Case Study using a Verilator SystemC Model of the OpenRISC 1000 Jeremy Bennett Embecosm Application Note 7. Issue 1 Published March 2009 Legal Notice This work is licensed under the Creative Commons Attribution 2.0 UK: England & Wales License. To view a copy of this license, visit http://creativecommons.org/licenses/by/2.0/uk/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. This license means you are free: • to copy, distribute, display, and perform the work • to make derivative works under the following conditions: • Attribution. You must give the original author, Jeremy Bennett of Embecosm (www.embecosm.com), credit; • For any reuse or distribution, you must make clear to others the license terms of this work; • Any of these conditions can be waived if you get permission from the copyright holder, Embecosm; and • Nothing in this license impairs or restricts the author's moral rights. The software for the SystemC cycle accurate model written by Embecosm and used in this document is licensed under the GNU General Public License (GNU General Public License). For detailed licensing information see the file COPYING in the source code. Embecosm is the business name of Embecosm Limited, a private limited company registered in England and Wales. Registration number 6577021. ii Copyright © 2009 Embecosm Limited Table of Contents 1. Introduction ................................................................................................................ 1 1.1. Why Use Cycle Accurate Modeling .................................................................... 1 1.2. Target Audience ................................................................................................ 1 1.3. Open Source ..................................................................................................... 2 1.4. Further Sources of Information ......................................................................... 2 1.4.1.
    [Show full text]
  • Jaké Je to Vyvíjet Prekladace?
    Jak to zacalo?ˇ What’s GNU? Gnu’s Not Unix! AMD64 port a SUSE GCC dnes Jaké je to vyvíjet prekladaˇ ce?ˇ Jan Hubickaˇ Katedra aplikované matematiky Filosofické problémy informatiky Jak to zacalo?ˇ What’s GNU? Gnu’s Not Unix! AMD64 port a SUSE GCC dnes Co je GCC GNU Compiler collection: • Prekladaˇ cˇ C, C++, obj-C, obj-C++, Fortranu, Ady, Go,. • Podporující více než 50 procesor˚ua nekolikˇ set target˚u(kombinací procesor+OS) • Vyvjený od 80. let jako jeden ze základních balík˚uGNU projektu • První verze vydaná v roce 1987 • Verze 8 vyjde tento týden? • 10m rádek,ˇ cca 100-150 aktivních vývojár˚u,odhademˇ 2000 clovˇ ekoletˇ Hacker na MIT od 1971. V záríˇ 1983 oznamuje GNU operating system. 1984 ochází a venujeˇ se GNU projektu. Zacalˇ vyvíjet základní nástroje Emacs, GCC, GDB, make, . Jak to zacalo?ˇ What’s GNU? Gnu’s Not Unix! AMD64 port a SUSE GCC dnes Richard Mathew Stallman (RMS) vs Xerox 9700 Hacker na MIT od 1971. V záríˇ 1983 oznamuje GNU operating system. 1984 ochází a venujeˇ se GNU projektu. Zacalˇ vyvíjet základní nástroje Emacs, GCC, GDB, make, . Jak to zacalo?ˇ What’s GNU? Gnu’s Not Unix! AMD64 port a SUSE GCC dnes Richard Mathew Stallman (RMS) vs Xerox 9700 Jak to zacalo?ˇ What’s GNU? Gnu’s Not Unix! AMD64 port a SUSE GCC dnes Richard Mathew Stallman (RMS) vs Xerox 9700 Hacker na MIT od 1971. V záríˇ 1983 oznamuje GNU operating system. 1984 ochází a venujeˇ se GNU projektu. Zacalˇ vyvíjet základní nástroje Emacs, GCC, GDB, make, .
    [Show full text]
  • GNU / Linux and Free Software
    GNU / Linux and Free Software GNU / Linux and Free Software An introduction Michael Opdenacker Free Electrons http://free-electrons.com Created with OpenOffice.org 2.x GNU / Linux and Free Software © Copyright 2004-2007, Free Electrons Creative Commons Attribution-ShareAlike 2.5 license http://free-electrons.com Sep 15, 2009 1 Rights to copy Attribution ± ShareAlike 2.5 © Copyright 2004-2007 You are free Free Electrons to copy, distribute, display, and perform the work [email protected] to make derivative works to make commercial use of the work Document sources, updates and translations: Under the following conditions http://free-electrons.com/articles/freesw Attribution. You must give the original author credit. Corrections, suggestions, contributions and Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license translations are welcome! identical to this one. For any reuse or distribution, you must make clear to others the license terms of this work. Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. License text: http://creativecommons.org/licenses/by-sa/2.5/legalcode GNU / Linux and Free Software © Copyright 2004-2007, Free Electrons Creative Commons Attribution-ShareAlike 2.5 license http://free-electrons.com Sep 15, 2009 2 Contents Unix and its history Free Software licenses and legal issues Free operating systems Successful project highlights Free Software
    [Show full text]
  • Free As in Freedom (2.0): Richard Stallman and the Free Software Revolution
    Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution Sam Williams Second edition revisions by Richard M. Stallman i This is Free as in Freedom 2.0: Richard Stallman and the Free Soft- ware Revolution, a revision of Free as in Freedom: Richard Stallman's Crusade for Free Software. Copyright c 2002, 2010 Sam Williams Copyright c 2010 Richard M. Stallman Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License." Published by the Free Software Foundation 51 Franklin St., Fifth Floor Boston, MA 02110-1335 USA ISBN: 9780983159216 The cover photograph of Richard Stallman is by Peter Hinely. The PDP-10 photograph in Chapter 7 is by Rodney Brooks. The photo- graph of St. IGNUcius in Chapter 8 is by Stian Eikeland. Contents Foreword by Richard M. Stallmanv Preface by Sam Williams vii 1 For Want of a Printer1 2 2001: A Hacker's Odyssey 13 3 A Portrait of the Hacker as a Young Man 25 4 Impeach God 37 5 Puddle of Freedom 59 6 The Emacs Commune 77 7 A Stark Moral Choice 89 8 St. Ignucius 109 9 The GNU General Public License 123 10 GNU/Linux 145 iii iv CONTENTS 11 Open Source 159 12 A Brief Journey through Hacker Hell 175 13 Continuing the Fight 181 Epilogue from Sam Williams: Crushing Loneliness 193 Appendix A { Hack, Hackers, and Hacking 209 Appendix B { GNU Free Documentation License 217 Foreword by Richard M.
    [Show full text]
  • Anthony J. Massa
    EMBEDDED SOFTWARE DEVELOPMENT WITH ECOS™ Anthony J. Massa EMBEDDED SOFTWARE DEVELOPMENT WITH ECOS Anthony J. Massa PRENTICE HALL PROFESSIONAL TECHNICAL REFERENCE UPPER SADDLE RIVER, NJ 07458 WWW.PHPTR.COM WWW.PHPTR.COM/MASSA/ Library of Congress Cataloging-in-Publication Data Massa, Anthony J. Embedded software development with eCos / Anthony J. Massa p. cm.--(Bruce Perens' Open source series) ISBN 0-13-035473-2 1. Embedded computer systems--Programming. 2. Application software--Development. 3. Real-time data processing. I. Title. II. Series. QA76.6 .M364317 2002 005.26--dc21 2002035507 Editorial/production supervision: Techne Group Cover design director: Jerry Votta Cover design: Anthony Gemmellaro Art director: Gail Cocker-Bogusz Interior design: Meg Van Arsdale Manufacturing buyer: Maura Zaldivar Editor-in-Chief: Mark L. Taub Editorial assistant: Kate Wolf Marketing manager: Bryan Gambrel Full-service production manager: Anne R. Garcia © 2003 Pearson Education, Inc. Publishing as Prentice Hall Professional Technical Reference Upper Saddle River, New Jersey 07458 This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at <http://www.opencontent.org/openpub/>). Prentice Hall books are widely used by corporations and government agencies for training, marketing, and resale. For information regarding corporate and government bulk discounts please contact: Corporate and Government Sales (800) 382-3419 or [email protected] Other company and product names mentioned herein are the trademarks or registered trademarks of their respective owners. All rights reserved. No part of this book may be reproduced, in any form or by any means, without permission in writing from the publisher.
    [Show full text]
  • Embedded Configurable Operating System
    eCos Embedded Configurable Operating System Embedded Track – FOSDEM 2003 Nick Garnett – Copyright © 2003 eCosCentric Features • Open Source • Royalty Free • Highly Configurable • Very Portable • Real Time • Small Footprint • Standards • Networking Embedded Track – FOSDEM 2003 Nick Garnett – Copyright © 2003 eCosCentric History • Cygnus Solutions – 1997 Project started – 1998 First release • Red Hat – 1999 Cygnus acquired by Red Hat – 2000 RedBoot added – 2002 Red Hat lay off eCos team • eCosCentric – 2002 eCos team form eCosCentric Embedded Track – FOSDEM 2003 Nick Garnett – Copyright © 2003 eCosCentric Licensing • RHEPL – Red Hat eCos Public License – Allowed proprietary code to be linked with eCos – Required all changes to be returned to Red Hat • GPL + exception – Standard GPL – Exception allows non-GPL code to be linked with eCos – No change requirement – No “plain” GPL code allowed in eCos Embedded Track – FOSDEM 2003 Nick Garnett – Copyright © 2003 eCosCentric Configuration • Packages – Separate package for each subsystem – Independently selectable – Self describing • Component Description Language – Describes features provided by package – Describes features required by package • Inference Engine – Automatic resolution of constraints Embedded Track – FOSDEM 2003 Nick Garnett – Copyright © 2003 eCosCentric Configuration Tools • GUI Configuration Tool – wxWindows based – Linux and Windows NT/2000/XP – Includes build and test systems – Large and small scale configuration • Command line Tool – Linux and Windows (Cygwin) – Automation
    [Show full text]
  • A Highly Configurable Operating System - Ecos
    A highly configurable operating system - eCos Shilei He Department of computer science and engineering Aalto University Helsinki, Finland [email protected] Abstract— This paper introduces an embedded maintainer of eCos and laid off the developing team. configurable operating system – eCos. It describes the Nevertheless, some of the laid off employees continued the background and functionality of eCos; and it gives a deep work of eCos and made their business by providing services discussion of its configuration method, which is the key for eCos. According to the request from eCos development innovation technology and making eCos distinguish from other community, Red Hat agreed to transfer the ownership and operating systems. Moreover, it compares the memory maintenance of eCos to Free Software Foundation [6]. With requirement and kernel performance between eCos and the feature of open sourse, eCos had to be royalty-free, in traditional operating systems. other words, eCos was abled to be developed with no initial cost which reduced the costs for embedded products [3]. Keywords—eCos; Real Time Operating Systems; Open Source Software; High configurable RTOS III. ECOS ARCHITECTURE I. INTRODUCTION eCos (embedded configurable operating system) [4] is an With the development of science and technology, open source real-time operating system intended for embedded operating systems are widely used in many fields, embedded applications, and it is supported by the GNU open source development tools. eCos made the innovation on its such as military, industry and electric equipment. This paper highly configurable system, which allows the developers to introduces an embedded configurable operating system – create customized applications with precise requirements.
    [Show full text]
  • Selected Essays of Richard M. Stallman
    Free Software, Free Society: Selected Essays of Richard M. Stallman Introduction by Lawrence Lessig Edited by Joshua Gay GNU Press www.gnupress.org Free Software Foundation Boston, MA USA First printing, first edition. Copyright © 2002 Free Software Foundation, Inc. ISBN 1-882114-98-1 Published by the Free Software Foundation 59 Temple Place Boston, MA Tel: 1-617-542-5942 Fax: 1-617-542-2652 Email: [email protected] Web: www.gnu.org GNU Press is an imprint of the FSF. Email: [email protected] Web: www.gnupress.org Please contact the GNU Press for information regarding bulk purchases for class- room or user group use, reselling, or any other questions or comments. Original artwork by Etienne Suvasa. Cover design by Jonathan Richard. Permission is granted to make and distribute verbatim copies of this book provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute translations of this book into another language, from the original English, with respect to the conditions on distribution of modified versions above, provided that it has been approved by the Free Software Foundation. i Short Contents Editor’s Note................................................ 1 A Note on Software .......................................... 3 Topic Guide ................................................ 7 Introduction ............................................... 11 Section One ............................................... 15 1 The GNU Project ....................................... 17 2 The GNU Manifesto ..................................... 33 3 Free Software Definition ................................. 43 4 Why Software Should Not Have Owners ..................... 47 5 What’s in a Name? ...................................... 53 6 Why “Free Software” is Better than “Open Source” ............ 57 7 Releasing Free Software if You Work at a University ........... 63 8 Selling Free Software ...................................
    [Show full text]
  • The Definitive Guide to GCC
    The Definitive Guide to GCC KURT WALL AND WILLIAM VON HAGEN APress Media, LLC The Definitive Guide to GCC Copyright ©2004 by Kurt Wall and William von Hagen Originally published by Apress in 2004 All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN 978-1-59059-109-3 ISBN 978-1-4302-0704-7 (eBook) DOI 10.1007/978-1-4302-0704-7 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Technical Reviewer: Gene Sally Editorial Board: Steve Anglin, Dan Appleman, Gary Cornell, James Cox, Tony Davis, John Franklin, Chris Mills, Steven Rycroft, Dominic Shakeshaft, Julian Skinner, Martin Streicher, Jim Sumser, Karen Watterson, Gavin Wray, John Zukowski Assistant Publisher: Grace Wong Project Manager: Sofia Marchant Copy Editor: Ami Knox Production Manager: Kari Brooks Production Editor: Janet Vaii Proofreader: Elizabeth Berry Compositor and Artist: Kinetic Publishing Services, llC Indexer: Valerie Perry Cover Designer: Kurt Krames Manufacturing Manager: Tom Debolski The information in this book is distributed on an "as is" hasis, without warranty. Although every precaution bas been taken in the preparation of this work, neither the author(s) nor Apress shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the information contained in this work.
    [Show full text]
  • Gdb Internals a Guide to the Internals of the GNU Debugger
    gdb Internals A guide to the internals of the GNU debugger John Gilmore Cygnus Solutions Second Edition: Stan Shebs Cygnus Solutions Cygnus Solutions Revision TEXinfo 2007-09-03.05 Copyright c 1990-2013 Free Software Foundation, Inc. Contributed by Cygnus Solutions. Written by John Gilmore. Second Edition by Stan Shebs. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". i Table of Contents Scope of this Document :::::::::::::::::::::::::::: 1 1 Summary :::::::::::::::::::::::::::::::::::::::: 1 1.1 Requirements :::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Contributors ::::::::::::::::::::::::::::::::::::::::::::::::::: 1 2 Overall Structure ::::::::::::::::::::::::::::::: 2 2.1 The Symbol Side ::::::::::::::::::::::::::::::::::::::::::::::: 2 2.2 The Target Side :::::::::::::::::::::::::::::::::::::::::::::::: 2 2.3 Configurations ::::::::::::::::::::::::::::::::::::::::::::::::: 2 2.4 Source Tree Structure :::::::::::::::::::::::::::::::::::::::::: 3 3 Algorithms :::::::::::::::::::::::::::::::::::::: 4 3.1 Prologue Analysis :::::::::::::::::::::::::::::::::::::::::::::: 4 3.2 Breakpoint Handling ::::::::::::::::::::::::::::::::::::::::::: 6 3.3 Single Stepping ::::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]