DOCSLIB.ORG

PRACTICE Script Language Reference Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
PRACTICE Script Language Reference Guide PRACTICE Script Language Reference Guide TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... PRACTICE Script Language ......................................................................................................... PRACTICE Script Language Reference Guide ........................................................................ 1 History ...................................................................................................................................... 4 Related Documents ................................................................................................................. 5 A ... D ........................................................................................................................................ 6 APPEND Append to file 6 BEEP Acoustic signal 6 CLOSE Close file 7 CONTinue Continue PRACTICE script 7 DECRYPT Decrypts a text or binary file 8 DO Start PRACTICE script 9 DODECRYPT Execute encrypted PRACTICE script (*.cmm) 10 E ... F ......................................................................................................................................... 11 ECHO Write text and data to an AREA window (with format decoration) 11 ELSE Conditional script execution 13 ENCRYPT Encrypt a text or binary file 14 ENCRYPTDO Encrypt a PRACTICE script (*.cmm) 15 ENCRYPTPER Encrypt a PER file (*.per) 16 END Terminate PRACTICE scripts, etc. 17 ENDDO Return from a PRACTICE script 18 ENTER Window-based input 19 ENTRY Parameter passing 21 G ... H ........................................................................................................................................ 22 GLOBAL Create global PRACTICE macro 22 GLOBALON Global event-controlled PRACTICE script execution 23 GOSUB Subroutine call 29 GOTO Local script jump 30 I ... L .......................................................................................................................................... 31 IF Conditional script execution 31 INKEY Character input 32 JUMPTO Global script jump 32 LOCAL Create local PRACTICE macro 33 ©1989-2021 Lauterbach GmbH PRACTICE Script Language Reference Guide 1 M ... O ........................................................................................................................................ 35 ON Event-controlled PRACTICE script execution 35 OPEN Open data file 40 P ... ............................................................................................................................................ 41 PARAMETERS Parameter fetching 41 PBREAK Breakpoints in PRACTICE script files (*.cmm) 42 PBREAK.at Deprecated command - for backward compatibility reasons 42 PBREAK.Delete Delete breakpoint 43 PBREAK.DISable Disable breakpoint 43 PBREAK.ENable Enable breakpoint 44 PBREAK.List Display breakpoint list 45 PBREAK.OFF TRACE32 disables breakpoint handling 46 PBREAK.ON TRACE32 re-enables breakpoint handling 47 PBREAK.RESet Clear all breakpoints 47 PBREAK.Set Add breakpoint 48 PEDIT Edit PRACTICE script 51 PLIST List PRACTICE script 54 PMACRO PRACTICE macros 55 PMACRO.EXPLICIT Enforce explicit PRACTICE macro declaration 55 PMACRO.IMPLICIT Implicit PRACTICE macro declaration 57 PMACRO.list Display PRACTICE macros 58 PMACRO.LOCK Lock PRACTICE macros 58 PMACRO.RESet Clear current PRACTICE macros 59 PMACRO.UNLOCK Unlock PRACTICE macros 59 PRINT Write text and data to an AREA window (without format decoration) 60 PRINTF Write formatted data to an AREA window 64 PRIVATE Create private PRACTICE macro 72 PSKIP Skip command or block in PRACTICE script 74 PSTEP Execute single line 75 PSTEPOUT Back to caller 76 PSTEPOVER Step over callee and stop at the next script line 77 Q ... R ........................................................................................................................................ 78 READ Read from data file 78 RePeaT Loop with check at end of loop 79 RETURN Return from subroutine 81 RETURNVALUES Take return values 82 RUN Start PRACTICE script 83 S ... T ......................................................................................................................................... 84 SCREEN Screen updating 84 SCREEN.ALways Refresh always 84 SCREEN.display Refresh screen 85 SCREEN.OFF No refresh 85 ©1989-2021 Lauterbach GmbH PRACTICE Script Language Reference Guide 2 SCREEN.ON Refresh when printing 85 SCREEN.WAIT Update screen while waiting 86 SPRINTF Write formatted data to a PRACTICE macro 88 STOP Interrupt PRACTICE script 89 W ... Z ........................................................................................................................................ 90 WAIT Wait until a condition is true or a period has elapsed 90 WHILE Loop with check at start of loop 92 WRITE Write to data file 93 WRITEB Write binary data to file 94 ©1989-2021 Lauterbach GmbH PRACTICE Script Language Reference Guide 3 PRACTICE Script Language Reference Guide Version 30-Apr-2021 History 31-Jan-19 Revised the PEDIT command. ©1989-2021 Lauterbach GmbH PRACTICE Script Language Reference Guide 4 Related Documents For information about how to pass parameters, PRACTICE macros, etc., refer to: • “PRACTICE Script Language User’s Guide” (practice_user.pdf) For information about literals, operators, and operator precedence, refer to: • “PowerView User’s Guide” (ide_user.pdf). Alternatively, choose Help menu > Index, and then enter the search item. For information about functions, refer to: • “PowerView Function Reference” (ide_func.pdf) • “General Function Reference” (general_func.pdf) For information about the purpose of functions in TRACE32, how to use functions, and the difference between functions and commands, refer to: • “General Function Reference” (general_func.pdf) ;To retrieve the same information via the TRACE32 command line: HELP.Index "scripting" HELP.Index "literals" HELP.Index "operators" HELP.Index "operator precedence" HELP.Index "functions" ©1989-2021 Lauterbach GmbH PRACTICE Script Language Reference Guide 5 A...D APPEND Append to file Format: APPEND <file> <parameter_list> Appends data to a file. The file is created if it does not exist. The syntax of the command is similar to the PRINT command. Example: APPEND datafile.dat "Test" See also ■ CLOSE ■ MKTEMP ■ OPEN ■ WRITE ▲ ’Release Information’ in ’Release History’ BEEP Acoustic signal Format: BEEP [<sound_code>] Generates an acoustic signal on the host computer. The type of the sound depends on the host. To get more complex sounds on workstation hosts it is possible to execute operation system commands. Example: BEEP 5. See also ■ SETUP.SOUND ©1989-2021 Lauterbach GmbH PRACTICE Script Language Reference Guide 6 CLOSE Close file Format: CLOSE #<buffer_number> Closes an input or output file. Example: OPEN #1 ~~~/test.dat /Write ; open file for writing WRITE #1 "Test data" ; write data to file CLOSE #1 ; close file TYPE ~~~/test.dat ; optional: open file in TYPE window The path prefix ~~~ expands to the temporary directory of TRACE32. See also ■ APPEND ■ OPEN ■ READ ■ WRITE ■ WRITEB ■ Data.WRITESTRING ■ Var.WRITE CONTinue Continue PRACTICE script Format: CONTinue [[<line>] [<file>]] A PRACTICE script which has been stopped will be restarted at the current PRACTICE command. PRACTICE scripts will be stopped by the STOP command or by a breakpoint within the script. The CONTinue command can also be used to resume a script that has been halted due to an error condition. The wrong command may be replaced by an interactive command. <line> Line number. Go till <line> in the active PRACTICE script (*.cmm). , <file> Line number is omitted. Path and file name of PRACTICE script. Go till first executable line in the PRACTICE script <file>. <line> <file> Go till <line> in the PRACTICE script <file>. ©1989-2021 Lauterbach GmbH PRACTICE Script Language Reference Guide 7 Example 1: DO test.cmm ; start script … … … ; script stopped at breakpoint CONTinue ; continue Example 2: … STOP ; stop script by STOP command … … CONTinue ; continue See also ■ END ■ PBREAK ■ STOP DECRYPT Decrypts a text or binary file Format: DECRYPT <keystring> <encrypted_file> [<decrypted_file>] Uses the original key string to decrypt a text or binary file previously encrypted with the ENCRYPT command. The resulting file can get a new name or replace the old file. See also ■ ENCRYPT ▲ ’Encrypt/Execute Encrypted Files’ in ’PowerView User’s Guide’ ©1989-2021 Lauterbach GmbH PRACTICE Script Language Reference Guide 8 DO Start PRACTICE script Format: DO <file> [<parameter_list>] Starts a PRACTICE script (*.cmm). The DO command can be used on the command level to start a PRACTICE script or within a script to run another file like a subroutine. PRACTICE files started by a DO command should be terminated by the ENDDO command. Additional parameters may be defined which are passed to the subroutine. The subroutine reads the parameter list using the ENTRY command. Using the DO command even those settings saved by the STOre command can be retrieved. <file> The default extension for <file> is *.cmm. The default extension can be changed with the command SETUP.EXTension PRACTICE. Examples: ; store window setting to the PRACTICE file 'test.cmm' STOre test.cmm Win ; set up window setting by executing the script 'test.cmm' DO test.cmm ; Endless loop with subroutine call &count=1 WHILE TRUE() ( DO mem_test PRINT "MEMTEST " &count &count=&count+1 ) ENDDO ChDir.DO c:\sample\x.cmm ; change to c:\sample
Load more

Recommended publications
  • 7843 Directory Management
    7843 Directory Management Tired of using existing badly written operating systems, Hieu decided to write his new one. Of course, his new operating system will be awesome, bug-free, fast and easy to use. He has finished most of the work, and now he is asking you to do one lasttask: Implement a directory manager. Initially, Hieu’s computer directory is empty. The current directory is the root directory. The directory manager keeps the directory in a rooted-tree structure. In each directory, the children are sorted in lexicographical order. He can do one of the following actions: • MKDIR s: create a child directory named s inside the current directory where s is a string. – If the current directory already contains a child directory named s, print “ERR” and do nothing. – Otherwise, print “OK” • RM s: remove a child directory named s inside the current directory where s is a string. Figure 1 – If there is no child directory named s, print “ERR”. Otherwise, print “OK”. • CD s: change the current directory to a child directory named s where s is a string. – If s is equal to the string “..” and the current directory is the root directory, print “ERR” and do nothing. – If s is equal to the string “..” and the current directory is not the root direc- tory, then you need to change the current directory to the parent directory Figure 2 and print “OK”. – If there is no child directory named s, print “ERR” and do nothing. – If there is a child directory named s then you need to change the current directory to s and print “OK”.
    [Show full text]
  • Commands to Control Device
    Commands to Control Device New OTA firmware upgrade command. To try it via over-the-air update, use these commands: > fwe > fwd B6FMA186 The board will reboot after the first command, this is normal. After the second command wait 1-3 minutes (seems like a long time). After it resets again, go back to BlueFruit and press "info" the software should be 3.0.186 The default wakeup interval is still 4 hours (14400 seconds). To configure a unit for a different wakeup interval: >wakt 600 (this would be 60*10 = 10 minutes) No beeps (Command to turn off the beeps) nvap 6 120000 14400000 15000 5000 0 223 1 3 Command to Restore Beeps nvap 6 120000 14400000 15000 5000 0 223 1 65535 Main Menu commands ---- SubMenus -------------------------- >i - I2C menu >l - Log menu >M - Modem menu ---- Device Control Cmds --------------- >D [n] - set debug level to [n] >info - Show device info >cota - CDMA OTA reprovision >svrm [name] - Set server main >nvmr - Non-volatile memory revert >t - show system uptime >rst - Hard reset ---- General Cmds ---------------------- >c [str] - Execute remote command manually >batq - Query battery state >slp - Go to sleep immediately >slpt [n] - Set sleep timeout to [n] seconds >wakt [n] - Set wake timeout to [n] hours >sus - Suspend immediately >sts - Show statistics and send to server >bt [n] - Bluetooth disable/enable: n=0/1 >dsms [n] - DebugSMS configure 0/1=disabled/enabled >wss [p] [s] - WiMM Server Send [p]ort, [s]tring >wsr - WiMM Server Recv ---- Pos/Log Cmds ---------------------- >pn - Position now >plc {i} {t} - Position log ctrl, [i]nterval, [t]ripId Stop Logging >pla {i} {t} - Position log auto, [i]nterval, [t]ripId >plb {n} - Position log batch [n] records >ple - Position log erase --- Alarm Cmds ------------------------ >alm [m] - Alarm mode: m=0/1/2: Off/On/FireNow ---- Firmware Cmds --------------------- >fwd [v] - Firmware Download (WIMM{v}.hex) >fwl {i} - Firmware Launch (i=0/1: ImgA/B) >fwe - Firmware Erase (ImgB) To change the alarm delay You must be running firmware 145 or later.
    [Show full text]
  • KDE 2.0 Development, Which Is Directly Supported
    23 8911 CH18 10/16/00 1:44 PM Page 401 The KDevelop IDE: The CHAPTER Integrated Development Environment for KDE by Ralf Nolden 18 IN THIS CHAPTER • General Issues 402 • Creating KDE 2.0 Applications 409 • Getting Started with the KDE 2.0 API 413 • The Classbrowser and Your Project 416 • The File Viewers—The Windows to Your Project Files 419 • The KDevelop Debugger 421 • KDevelop 2.0—A Preview 425 23 8911 CH18 10/16/00 1:44 PM Page 402 Developer Tools and Support 402 PART IV Although developing applications under UNIX systems can be a lot of fun, until now the pro- grammer was lacking a comfortable environment that takes away the usual standard activities that have to be done over and over in the process of programming. The KDevelop IDE closes this gap and makes it a joy to work within a complete, integrated development environment, combining the use of the GNU standard development tools such as the g++ compiler and the gdb debugger with the advantages of a GUI-based environment that automates all standard actions and allows the developer to concentrate on the work of writing software instead of managing command-line tools. It also offers direct and quick access to source files and docu- mentation. KDevelop primarily aims to provide the best means to rapidly set up and write KDE software; it also supports extended features such as GUI designing and translation in con- junction with other tools available especially for KDE development. The KDevelop IDE itself is published under the GNU Public License (GPL), like KDE, and is therefore publicly avail- able at no cost—including its source code—and it may be used both for free and for commer- cial development.
    [Show full text]
  • Print Wizard 3 Manual
    Print Wizard User Guide and Technical Manual Version 3.0 and later Rasmussen Software, Inc. 10240 SW Nimbus Ave., Suite L9, Portland, Oregon 97223 (503) 624-0360 www.anzio.com [email protected] Copyright © 2004-2005 by Rasmussen Software, Inc., All Rights Reserved Rasmussen Software, Inc. Page 1 Print Wizard Manual Table of Contents Table of Contents PRINT WIZARD USER GUIDE.......................................................................................................................................... 7 1 PRINT WIZARD INTRODUCTION ......................................................................................................................................... 7 1.1 What is Print Wizard?............................................................................................................................................... 7 1.2 Concept..................................................................................................................................................................... 7 1.3 Profiles and Services .............................................................................................................................................. 10 1.3.1 Introduction to print profiles................................................................................................................................................11 1.3.2 Introduction to services .......................................................................................................................................................12
    [Show full text]
  • Fundamentals of UNIX Lab 5.4.6 – Listing Directory Information (Estimated Time: 30 Min.)
    Fundamentals of UNIX Lab 5.4.6 – Listing Directory Information (Estimated time: 30 min.) Objectives: • Learn to display directory and file information • Use the ls (list files) command with various options • Display hidden files • Display files and file types • Examine and interpret the results of a long file listing • List individual directories • List directories recursively Background: In this lab, the student will use the ls command, which is used to display the contents of a directory. This command will display a listing of all files and directories within the current directory or specified directory or directories. If no pathname is given as an argument, ls will display the contents of the current directory. The ls command will list any subdirectories and files that are in the current working directory if a pathname is specified. The ls command will also default to a wide listing and display only file and directory names. There are many options that can be used with the ls command, which makes this command one of the more flexible and useful UNIX commands. Command Format: ls [-option(s)] [pathname[s]] Tools / Preparation: a) Before starting this lab, the student should review Chapter 5, Section 4 – Listing Directory Contents b) The student will need the following: 1. A login user ID, for example user2, and a password assigned by their instructor. 2. A computer running the UNIX operating system with CDE. 3. Networked computers in classroom. Notes: 1 - 5 Fundamentals UNIX 2.0—-Lab 5.4.6 Copyright 2002, Cisco Systems, Inc. Use the diagram of the sample Class File system directory tree to assist with this lab.
    [Show full text]
  • Administering Unidata on UNIX Platforms
    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniData Administering UniData on UNIX Platforms UDT-720-ADMU-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July, 2008 Book number: UDT-720-ADMU-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2010. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii SB/XA Getting Started The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
    [Show full text]
  • (2) G: 9 Timeout Error Layer —T
    US007831732B1 (12) United States Patent (10) Patent No.: US 7,831,732 B1 Zilist et al. (45) Date of Patent: Nov. 9, 2010 (54) NETWORK CONNECTION UTILITY 6,018,724 A 1/2000 Arent 6,182,139 B1 1/2001 Brendel ...................... TO9,226 (75) Inventors: Ira Zilist, Chicago, IL (US); Daniel 6,338,094 B1* 1/2002 Scott et al. .................. 709/245 Reimann, Mt. Prospect, IL (US); Devin 6,393,581 B1 5, 2002 Friedman et al. 6,731,625 B1 5/2004 Eastep et al. Henkel, Chicago, IL (US); Gurpreet 6,742,015 B1 5/2004 Bowman-Amuah Singh, Clarendon Hills, IL (US) 7,082,454 B1* 7/2006 Gheith ....................... TO9,203 2002/0120800 A1* 8/2002 Sugahara et al. .. ... 710,260 (73) Assignee: Federal Reserve Bank of Chicago, 2004/0010546 A1* 1/2004 Kluget al. ............ ... 709,203 Chicago, IL (US) 2004/0192383 A1* 9, 2004 Zacks et al. ................. 455/557 (*) Notice: Subject to any disclaimer, the term of this patent is extended or adjusted under 35 * cited by examiner U.S.C. 154(b) by 1196 days. Primary Examiner Ario Etienne Assistant Examiner Avi Gold (21) Appl. No.: 11/192,991 (74) Attorney, Agent, or Firm—Brinks Hofer Gilson & Lione (22) Filed: Jul. 29, 2005 (57) ABSTRACT Int. C. (51) A system is disclosed for masking errors that may occur G06F 15/16 (2006.01) during a delay of a client connecting with a server on a (52) U.S. Cl. ........................ 709/237; 709/217; 709/219 network. A connection utility requests a connection with the (58) Field of Classification Search ................
    [Show full text]
  • Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4
    SUSE Linux Enterprise Server 12 SP4 Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4 Provides information about how to manage storage devices on a SUSE Linux Enterprise Server. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xii 1 Available Documentation xii 2 Giving Feedback xiv 3 Documentation Conventions xiv 4 Product Life Cycle and Support xvi Support Statement for SUSE Linux Enterprise Server xvii • Technology Previews xviii I FILE SYSTEMS AND MOUNTING 1 1 Overview
    [Show full text]
  • System Calls System Calls
    System calls We will investigate several issues related to system calls. Read chapter 12 of the book Linux system call categories file management process management error handling note that these categories are loosely defined and much is behind included, e.g. communication. Why? 1 System calls File management system call hierarchy you may not see some topics as part of “file management”, e.g., sockets 2 System calls Process management system call hierarchy 3 System calls Error handling hierarchy 4 Error Handling Anything can fail! System calls are no exception Try to read a file that does not exist! Error number: errno every process contains a global variable errno errno is set to 0 when process is created when error occurs errno is set to a specific code associated with the error cause trying to open file that does not exist sets errno to 2 5 Error Handling error constants are defined in errno.h here are the first few of errno.h on OS X 10.6.4 #define EPERM 1 /* Operation not permitted */ #define ENOENT 2 /* No such file or directory */ #define ESRCH 3 /* No such process */ #define EINTR 4 /* Interrupted system call */ #define EIO 5 /* Input/output error */ #define ENXIO 6 /* Device not configured */ #define E2BIG 7 /* Argument list too long */ #define ENOEXEC 8 /* Exec format error */ #define EBADF 9 /* Bad file descriptor */ #define ECHILD 10 /* No child processes */ #define EDEADLK 11 /* Resource deadlock avoided */ 6 Error Handling common mistake for displaying errno from Linux errno man page: 7 Error Handling Description of the perror () system call.
    [Show full text]
  • Disk Clone Industrial
    Disk Clone Industrial USER MANUAL Ver. 1.0.0 Updated: 9 June 2020 | Contents | ii Contents Legal Statement............................................................................... 4 Introduction......................................................................................4 Cloning Data.................................................................................................................................... 4 Erasing Confidential Data..................................................................................................................5 Disk Clone Overview.......................................................................6 System Requirements....................................................................................................................... 7 Software Licensing........................................................................................................................... 7 Software Updates............................................................................................................................. 8 Getting Started.................................................................................9 Disk Clone Installation and Distribution.......................................................................................... 12 Launching and initial Configuration..................................................................................................12 Navigating Disk Clone.....................................................................................................................14
    [Show full text]
  • Using the GNU Debugger (Gdb) a Debugger Is a Very Useful Tool for Finding Bugs in a Program
    Using the GNU debugger (gdb) A debugger is a very useful tool for finding bugs in a program. You can interact with a program while it is running, start and stop it whenever, inspect the current values of variables and modify them, etc. If your program runs and crashes, it will produce a ‘core dump’. You can also use a debugger to look at the core dump and give you extra information about where the crash happened and what triggered it. Some debuggers (including recent versions of gdb) can also go backwards through your code: you run your code forwards in time to the point of an error, and then go backwards looking at the values of the key variables until you get to the start of the error. This can be slow but useful sometimes! To use a debugger effectively, you need to get the compiler to put extra ‘symbol’ information into the binary, otherwise all it will contain is machine code level – it is much more useful to have the actual variable names you used. To do this, you use: gfortran –g –O0 mycode.f90 –o mybinary where ‘-g’ is the compiler option to include extra symbols, -O0 is no optimization so the code is compiled exactly as written, and the output binary is called ’mybinary’. If the source files and executable file is in the same directory, then you can run the binary through the debugger by simply doing: gdb ./mybinary This will then put you into an interactive debugging session. Most commands can be shortened (eg ‘b’ instead of ‘break’) and pressing ‘enter’ will repeat the last command.
    [Show full text]
  • Package 'Slurmr'
    Package ‘slurmR’ September 3, 2021 Title A Lightweight Wrapper for 'Slurm' Version 0.5-1 Description 'Slurm', Simple Linux Utility for Resource Management <https://slurm.schedmd.com/>, is a popular 'Linux' based software used to schedule jobs in 'HPC' (High Performance Computing) clusters. This R package provides a specialized lightweight wrapper of 'Slurm' with a syntax similar to that found in the 'parallel' R package. The package also includes a method for creating socket cluster objects spanning multiple nodes that can be used with the 'parallel' package. Depends R (>= 3.3.0), parallel License MIT + file LICENSE BugReports https://github.com/USCbiostats/slurmR/issues URL https://github.com/USCbiostats/slurmR, https://slurm.schedmd.com/ Encoding UTF-8 RoxygenNote 7.1.1 Suggests knitr, rmarkdown, covr, tinytest Imports utils VignetteBuilder knitr Language en-US NeedsCompilation no Author George Vega Yon [aut, cre] (<https://orcid.org/0000-0002-3171-0844>), Paul Marjoram [ctb, ths] (<https://orcid.org/0000-0003-0824-7449>), National Cancer Institute (NCI) [fnd] (Grant Number 5P01CA196569-02), Michael Schubert [rev] (JOSS reviewer, <https://orcid.org/0000-0002-6862-5221>), Michel Lang [rev] (JOSS reviewer, <https://orcid.org/0000-0001-9754-0393>) Maintainer George Vega Yon <[email protected]> Repository CRAN Date/Publication 2021-09-03 04:20:02 UTC 1 2 expand_array_indexes R topics documented: expand_array_indexes . .2 JOB_STATE_CODES . .3 makeSlurmCluster . .4 new_rscript . .6 opts_slurmR . .7 parse_flags . .9 random_job_name . .9 read_sbatch . 10 slurmR . 11 slurmr_docker . 11 slurm_available . 12 Slurm_clean . 15 Slurm_collect . 16 Slurm_env . 17 Slurm_EvalQ . 18 slurm_job . 19 Slurm_log . 21 Slurm_Map . 22 snames . 25 sourceSlurm . 25 status . 28 the_plan .
    [Show full text]