DOCSLIB.ORG

Lldb Cheat Sheet

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Lldb Cheat Sheet >si >br s -f foo.c -l 12 show contents of variable bar lldb cheat sheet instruction level single step over set a breakpoint by regular expression on >frame variable bar Execution Commands >thread step-inst-over source file contents >fr v bar >ni >p bar start lld (prefix with xcrun on os x) >breakpoint set --source-pattern regular-expression --file SourceFile >lldb [program.app] step out of the currently selected frame show contents of var bar formatted as hex >br s -p regular-expression -f file >lldb -- program.app arg1 >thread step-out >frame variable --format x bar >finish >fr v -f x bar load program set conditional breakpoint >file program.app Return from currently frame, with return >breakpoint set --name foo -- show contents of global variable baz value condition '(int)strcmp(y,"hello") == >target variable baz run program 0' >thread return [RETURN EXPRESSION] >ta v baz >process launch [-- args] >br s -n foo -c >run [args] Backtrace and disassemble every time you '(int)strcmp(y,"hello") == 0' show global/static variables in current file >target variable stop set arguments list breakpoints >ta v >settings set target.run-args 1 >target stop-hook add >breakpoint list >bt >br l show argc and argv every time you stop launch process in new terminal >disassemble --pc >target stop-hook add --one-liner >process launch --tty -- <args> >DONE delete a breakpoint "frame variable argc argv" >breakpoint delete 1 >ta st a -o "fr v argc argv" set env variables run until line 12 or end of frame >br del 1 >display argc >settings set target.env-vars DEBUG=1 >thread until 12 Watchpoint Commands >display argv remove env variables Breakpoint Commands >settings remove target.env-vars set watchpoint on variable when written to display argc and argv when stopping in main DEBUG set breakpoint at all functions named main >watchpoint set variable global_var >target stop-hook add --name main -- >breakpoint set --name main >wa s v global_var one-liner "frame variable argc argv" show program arguments >br s -n main >ta st a -n main -o "fr v argc argv" >settings show target.run-args >b main set watchpoint on memory of pointer size >watchpoint set expression -- display *this when in class MyClass set env variable and run set breakpoint in file test.c line 12 0x123456 >target stop-hook add --classname >process launch -v DEBUG=1 >breakpoint set --file test.c --line >wa s e -- 0x123456 MyClass --one-liner "frame variable attach to process by PID 12 *this" set watchpoint on memory of custom size >ta st a -c MyClass -o "fr v *this" >process attach --pid 123 >br s -f test.c -l 12 > watchpoint set expression –x >b test.c:12 Evaluating Expressions attach to process by name byte_size -- 0x123456 >process attach --name a.out [-- set breakpoint at all C++ methods with name > wa s e –x byte_size -- 0x123456 evaluate expression (print alias possible as waitfor] main well) >breakpoint set --method main set a condition on a watchpoint >expr (int) printf ("Print nine: attach to remote gdb on eorgadd >br s -M main >watch set var global >gdb-remote eorgadd:8000 >watchpoint modify -c '(global==5)' %d.", 4 + 5) set breakpoint at ObjC function >print (int) printf ("Print nine: attach to gdb server on localhost >breakpoint set --name "-[NSString list watchpoints %d.", 4 + 5) >gdb-remote 8000 >watchpoint list stringWithFormat:]" using a convenience variable >b -[NSString stringWithFormat:] >watch l attach to remote Darwin kernel in kdp mode >expr unsigned int $foo = 5 >kdp-remote eorgadd delete a watchpoint set breakpoint at all ObjC functions whose print the ObjC description of an object selector is count >watchpoint delete 1 source level single step >watch del 1 >expr -o -- [SomeClass >thread step-in >breakpoint set --selector count returnAnObject] >step >br s -S count Examining Variables >po [SomeClass returnAnObject] >s set breakpoint by regular expression function show arguments and local variables print dynamic type of expression result source level setop over name >frame variable >expr -d 1 -- [SomeClass >thread step-over >breakpoint set --func-regex print.* >fr v returnAnObject] >next ensure that breakpoints by file and line work show local variables >expr -d 1 – >n someCPPObjectPtrOrReference (c/cpp/objc) >frame variable --no-args instruction level single step >settings set target.inline- >fr v -a >thread step-inst breakpoint-strategy always set dynamic type printing as default show general purpose registers as signed get information about specific heap Executable and Shared Library Query >settings set target.prefer-dynamic decimal allocation and cast result to dynamic type Commands run-target >register read --format i that can be deduced (Mac OS X only) list the main executable and all dependent >re r -f i >command script import calling a function with a breakpoint shared libraries >expr -i 0 -- >register read/d lldb.macosx.heap >image list function_with_a_breakpoint() show all registers in all register threads >malloc_info --type 0x10010d680 look up information for a raw address in the calling a function that crashes >register read --all find all heap blocks that contain pointer expr -u 0 -- function_which_crashes() >re r -a specified by an expression EXPR (Mac OS X executable or any shared libraries >image lookup --address 0x1ec4 show registers rax, rsp, rbp only) Examining Thread State >im loo -a 0x1ec4 register read rax rsp rbp >command script import show backtrace (current thread) lldb.macosx.heap look up functions matching a regular show register rax with binary format >thread backtrace >ptr_refs EXPR expression in a binary >bt >register read --format binary rax find all heap blocks that contain a C string >image lookup -r -n <FUNC_REGEX> read memory from 0xbffff3c0 and show 4 hex show backtrace for all threads anywhere in the block (Mac OS X only) (debug symbols) uint32_t values >image lookup -r -s <FUNC_REGEX> >thread backtrace all >command script import >memory read --size 4 --format x -- (non-debug syms) >bt all lldb.macosx.heap count 4 0xbffff3c0 >cstr_refs CSTRING find full source line information backtrace the first 5 frames of current thread >me r -s4 -fx -c4 0xbffff3c0 >image lookup -v --address 0x1ec4 >thread backtrace -c 5 >x -s4 -fx -c4 0xbffff3c0 disassemble current function for current (look for entryline) >bt 5 (lldb-169 and later) >memory read/4xw 0xbffff3c0 frame >bt –c 5 (lldb-168 and later) >x/4xw 0xbffff3c0 >disassemble –frame look up information for an address in a.out select a different stack frame by index >memory read --gdb-format 4xw >di -f only 0xbffff3c0 >frame select 12 disassemble any functions named main >image lookup --address 0x1ec4 a.out >im loo -a 0x1ec4 a.out >fr s 12 read memory starting at the expression >disassemble --name main >f 12 "argv[0]" >di -n main look up information for a type Pointer by show frame information >memory read `argv[0]` disassemble address range name >frame info >memory read --size `sizeof(int)` >disassemble --start-address 0x1eb8 - >image lookup --type Point `argv[0]` select stack frame the called current frame -end-address 0x1ec3 >im loo -t Point >up read 512 bytes from address 0xbffff3c0 and >di -s 0x1eb8 -e 0x1ec3 dump all sections from the main executable >frame select --relative=1 save results to a local file disassemble 20 instructions from start and any shared libraries select stack frame that is called by current >memory read --outfile /tmp/mem.txt - address >image dump sections -count 512 0xbffff3c0 >disassemble --start-address 0x1eb8 - frame >me r -o/tmp/mem.txt -c512 0xbffff3c0 dump all sections in the a.out module -count 20 >down >x/512bx -o/tmp/mem.txt 0xbffff3c0 >image dump sections a.out >frame select --relative=-1 >di -s 0x1eb8 -c 20 save binary memory data starting at 0x1000 dump all symbols from the main executable >fr s -r-1 show mixed source and disassembly for the and ending at 0x2000 to file and any shared libraries select different frame using relative offset current function >memory read --outfile /tmp/mem.bin - >image dump symtab >frame select --relative 2 >disassemble --frame –mixed -binary 0x1000 0x2000 >fr s -r2 >di -f -m dump all symbols in a.out and liba.so >me r -o /tmp/mem.bin -b 0x1000 >frame select --relative -3 >image dump symtab a.out liba.so 0x2000 >fr s -r-3 disassemble the current function for the current frame and show the opcode bytes Miscellaneous show general purpose registers get information about specific heap allocation (Mac OS X only) >disassemble --frame –bytes echo text to the screen >register read >di -f -b >command script import >script print "Here is some text" write 123 to register rax lldb.macosx.heap disassemble the current source line for the remap source file pathnames for the debug >register write rax 123 >process launch --environment current frame session (e.g. if program was built on another skip 8 bytes using with program counter MallocStackLogging=1 -- [ARGS] >disassemble --line PC) >malloc_info --stack-history >register write pc `$pc+8` >di -l >settings set target.source-map 0x10010d680 /buildbot/path /my/path .
Load more

Recommended publications
  • UNIX Shell Programming (15CS35) Solution Internal Assessment
    UNIX Shell Programming (15CS35) Solution Internal Assessment- II November - 2016 1. Explain significance of following commands (2x5=10 M) i. cp ?????? progs Wild card ? matches any single character, hence the above command (cp) copies files whose names are six in length to progs directory ii. ls *.[xyz]* Wild card * matches any number of characters, hence the above command (ls) lists all the files having extension as either x, or y or z. iii. ls jones[0-9][0- 9][0-9] In the above command the character class[0-9] matches any digit between 0 to 9. Hence the above command lists all the files beginning with jones and having last three characters as any digit between 0 to 9. iv. echo * The above command lists all the file in the current directory. v. cp foo foo* The above command copies the file foo to file called foo*. Here the wild card * loses its meaning. 1. Write UNIX commands for the following (2 X 5= 10 M) i. Find and replace all the occurrences of unix with UNIX in the file after confirming the user. : 1,$s/unix/UNIX/gc ii. List all the files in the current directory which names are having exactly 5 characters and any number of characters in their extension. ls ?????.* iii. Copy all files stored in /home/vtu with .c, .cpp and .java extensions to progs sub- directory in current directory cp /home/vtu/*.{c,cpp,java} ./progs iv. Delete all files containing agra or agar in their file names. rm *ag[ra][ar]* v.
    [Show full text]
  • Moxa Nport Real TTY Driver for Arm-Based Platform Porting Guide
    Moxa NPort Real TTY Driver for Arm-based Platform Porting Guide Moxa Technical Support Team [email protected] Contents 1 Introduction ...................................................................................2 2 Porting to the Moxa UC-Series—Arm-based Computer ....................2 2.1 Build binaries on a general Arm platform ...................................................... 2 2.2 Cross-compiler and the Real TTY driver ........................................................ 3 2.3 Moxa cross-compiling interactive script......................................................... 4 2.4 Manually build the Real TTY driver with a cross-compiler ................................ 5 2.5 Deploy cross-compiled binary to target......................................................... 8 3 Porting to Raspberry Pi OS .............................................................9 4 Porting to the Yocto Project on Raspberry Pi ................................ 10 4.1 Prerequisite............................................................................................... 10 4.2 Create a Moxa layer for the Yocto Project..................................................... 11 4.3 Install a Moxa layer into the Yocto Project.................................................... 17 4.4 Deploy the Yocto image in Raspberry Pi ....................................................... 17 4.5 Start the Real TTY driver in Raspberry Pi ..................................................... 18 4.6 Set the default tty mapping to the Real TTY configuration ............................
    [Show full text]
  • Printing Printf: Formatted Printing
    Printing printf: formatted printing So far we have just been copying stuff from standard-in, files, pipes, etc to the screen or another file. Say I have a file with names and phone numbers. I would like to print it out with vertically aligned columns. (so my printout is not in the same format as the input file) File contents: Desired display: Bob 4929 Bob 4929 Chuck 4882 Chuck 4882 printf is a command from the C programming language to control printing. Shell script #!/bin/bash printf "Hello world.\n" a=`echo Hello world. | wc | nawk '{print $2}' ` printf "This phrase contains %d words\n" $a Run it alpaca.ceri.memphis.edu512:> printex.sh Hello world. This phrase contains 2 words alpaca.ceri.memphis.edu513:> #!/bin/bash printf "Hello world.\n" a=`echo Hello world. | wc | nawk '{print $2}' ` printf "This phrase contains %d words\n" $a We need the double quotes “ . “ to define an argument (the stuff inside the quotes) for printf. #!/bin/bash printf "Hello world.\n" a=`echo Hello world. | wc | nawk '{print $2}' ` printf "This phrase contains %d words\n" $a The argument in double quotes has - Regular text (“Hello world”, “This text contains “) - Some funny new thing - %d – a format specifier. - The already known specification for a new line - \n #!/bin/bash printf "Hello world.\n" a=`echo Hello world. | wc | nawk '{print $2}' ` printf "This phrase contains %d words\n" $a We also have another argument, the $a, which is a shell variable, at the end. Note that the items are delimited with spaces, not commas.
    [Show full text]
  • Unix Commands (09/04/2014)
    Unix Commands (09/04/2014) • Access control – login <login_name> – exit – passwd <login_name> – yppassswd <loginname> – su – • Login as Super user – su <login> • Login as user <login> • Root Prompt – [root@localhost ~] # • User Prompt – [bms@raxama ~] $ On Line Documentation – man <command/topic> – info <command/topic> • Working with directories – mkdir –p <subdir> ... {-p create all directories in path if not present} mkdir –p /2015/Jan/21/14 will create /2015, Jan, 21 & 14 in case any of these is absent – cd <dir> – rm -r <subdir> ... Man Pages • 1 Executable programs or shell commands • 2 System calls (functions provided by the kernel) • 3 Library calls (functions within program libraries) • 4 Special files (usually found in /dev) • 5 File formats and conventions eg /etc/passwd • 6 Games • 7 Miscellaneous (including macro packages and conventions), e.g. man(7), groff(7) • 8 System administration commands (usually only for root) • 9 Kernel routines [Non standard] – man grep, {awk,sed,find,cut,sort} – man –k mysql, man –k dhcp – man crontab ,man 5 crontab – man printf, man 3 printf – man read, man 2 read – man info Runlevels used by Fedora/RHS Refer /etc/inittab • 0 - halt (Do NOT set initdefault to this) • 1 - Single user mode • 2 - Multiuser, – without NFS (The same as 3, if you do not have networking) • 3 - Full multi user mode w/o X • 4 - unused • 5 - X11 • 6 - reboot (Do NOT set init default to this) – init 6 {Reboot System} – init 0 {Halt the System} – reboot {Requires Super User} – <ctrl> <alt> <del> • in tty[2-7] mode – tty switching • <ctrl> <alt> <F1-7> • In Fedora 10 tty1 is X.
    [Show full text]
  • Gnu Coreutils Core GNU Utilities for Version 5.93, 2 November 2005
    gnu Coreutils Core GNU utilities for version 5.93, 2 November 2005 David MacKenzie et al. This manual documents version 5.93 of the gnu core utilities, including the standard pro- grams for text and file manipulation. Copyright c 1994, 1995, 1996, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 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”. Chapter 1: Introduction 1 1 Introduction This manual is a work in progress: many sections make no attempt to explain basic concepts in a way suitable for novices. Thus, if you are interested, please get involved in improving this manual. The entire gnu community will benefit. The gnu utilities documented here are mostly compatible with the POSIX standard. Please report bugs to [email protected]. Remember to include the version number, machine architecture, input files, and any other information needed to reproduce the bug: your input, what you expected, what you got, and why it is wrong. Diffs are welcome, but please include a description of the problem as well, since this is sometimes difficult to infer. See section “Bugs” in Using and Porting GNU CC. This manual was originally derived from the Unix man pages in the distributions, which were written by David MacKenzie and updated by Jim Meyering.
    [Show full text]
  • Processes in Linux/Unix
    Processes in Linux/Unix A program/command when executed, a special instance is provided by the system to the process. This instance consists of all the services/resources that may be utilized by the process under execution. • Whenever a command is issued in unix/linux, it creates/starts a new process. For example, pwd when issued which is used to list the current directory location the user is in, a process starts. • Through a 5 digit ID number unix/linux keeps account of the processes, this number is call process id or pid. Each process in the system has a unique pid. • Used up pid’s can be used in again for a newer process since all the possible combinations are used. • At any point of time, no two processes with the same pid exist in the system because it is the pid that Unix uses to track each process. Initializing a process A process can be run in two ways: 1. Foreground Process : Every process when started runs in foreground by default, receives input from the keyboard and sends output to the screen. When issuing pwd command $ ls pwd Output: $ /home/geeksforgeeks/root When a command/process is running in the foreground and is taking a lot of time, no other processes can be run or started because the prompt would not be available until the program finishes processing and comes out. 2. Backround Process : It runs in the background without keyboard input and waits till keyboard input is required. Thus, other processes can be done in parallel with the process running in background since they do not have to wait for the previous process to be completed.
    [Show full text]
  • Systems Supplement for COP 3601
    Systems Guide for COP 3601: Introduction to Systems Software Charles N. Winton Department of Computer and Information Sciences University of North Florida 2010 Chapter 1 A Basic Guide for the Unix Operating System 1. 1 Using the Unix On-line Manual Pages Facility The following are some of the Unix commands for which you may display manual pages: cal cat cd chmod cp cut date echo egrep ex fgrep file find gcc gdb grep kill less ln locate ls mail make man mesg mkdir mv nohup nl passwd pr ps pwd rm rmdir set sleep sort stty tail tee time touch tr tty uname umask unset vim wall wc which who whoami write For example, to display the manual pages for the command "cp" enter man cp Note that you may also enter man man to find out more about the "man" command. In addition there may be commands unique to the local environment with manual pages; e.g., man turnin accesses a manual page for a project submission utility named Aturnin@ that has been added to the system. If you enter a command from the Unix prompt that requires an argument, the system will recognize that the command is incomplete and respond with an error message. For example, if the command "cp" had been entered at the Unix prompt the system would respond with the information such as shown below: cp: missing file arguments Try `cp --help' for more information. The "cp" command is a copy command. If the arguments which tell the command which file to copy and where to locate the copied file are missing, then the usage error message is generated.
    [Show full text]
  • Tips for Riding Metro for People with Disabilities and Senior
    50.173 2/18 50.173 [email protected]. purchase one, call 202-962-2700 or email email or 202-962-2700 call one, purchase Metrobuses. Reduced Fare SmarTrip Fare Reduced ID and how to to how and ID disabilities. ® points on most most on points To find out if you’re eligible for a Metro Metro a for eligible you’re if out find To providing Metro services to individuals with with individuals to services Metro providing Eligibility Certification and Outreach at 202-962-2703. 202-962-2703. at Outreach and Certification Eligibility and transfer transfer and operate vehicles and equipment when when equipment and vehicles operate about Metro’s free travel training, Contact the Office of of Office the Contact training, travel free Metro’s about for locations. for intersections intersections don’t know how, let us show them. For more information information more For them. show us let how, know don’t sensitivity training and are trained to to trained are and training sensitivity Prince George’s counties. See wmata.com wmata.com See counties. George’s Prince announce stops, stops, announce who doesn’t use Metrobus or Metrorail because they they because Metrorail or Metrobus use doesn’t who Managers and Train Operators receive receive Operators Train and Managers select public libraries in Montgomery and and Montgomery in libraries public select audio systems systems audio If you know a senior citizen or someone with a disability disability a with someone or citizen senior a know you If Metrobus Operators and Metrorail Station Station Metrorail and Operators Metrobus at all Metro sales offices, transit stores and and stores transit offices, sales Metro all at Digital signs and and signs Digital The benefits are life-changing.
    [Show full text]
  • Shell Scripting
    Shell Scripting Alexander B. Pacheco LTS Research Computing Outline 1 Introduction Types of Shell Variables File Permissions Input and Output 2 Shell Scripting Getting Started with Writing Simple Scripts Arithmetic Operations Flow Control Arrays Command Line Arguments Functions 3 Unix Utilities grep sed 4 awk programming 5 Wrap Up 2 / 76 Introduction Introduction What is a SHELL The command line interface is the primary interface to Linux/Unix operating systems. Shells are how command-line interfaces are implemented in Linux/Unix. Each shell has varying capabilities and features and the user should choose the shell that best suits their needs. The shell is simply an application running on top of the kernel and provides a powerful interface to the system. her Softwa Ot re Shell Kernel rdwa a r e H 4 / 76 Types of Shell sh : Bourne Shell Developed by Stephen Bourne at AT&T Bell Labs csh : C Shell Developed by Bill Joy at University of California, Berkeley ksh : Korn Shell Developed by David Korn at AT&T Bell Labs backward-compatible with the Bourne shell and includes many features of the C shell bash : Bourne Again Shell Developed by Brian Fox for the GNU Project as a free software replacement for the Bourne shell (sh). Default Shell on Linux and Mac OSX The name is also descriptive of what it did, bashing together the features of sh, csh and ksh tcsh : TENEX C Shell Developed by Ken Greer at Carnegie Mellon University It is essentially the C shell with programmable command line completion, command-line editing, and a few other features.
    [Show full text]
  • CIS18A: Introduction to Linux/Unix CLASSROOM ATC
    http://voyager.deanza.fhda.edu/~lalitha/cis18a/cis18a.html CIS18A: Introduction to Linux/Unix CLASSROOM ATC 204 WINTER 2015 : Section INFO: 00444 CIS -018A-61Y College academic Calendar: Winter 2015 http://deanza.fhda.edu/calendar/winterdates.html Instructor Information Name: Lalitha Krishnamurthy Office Hours: Not applicable ie None Email: krishnamurthylalitha at fhda dot edu Online Lab Hours: Wednesdays 845PM-10PM Lecture timings for CIS18A : M/W 6 PM - 750 PM Course Description This course is designed to discuss Linux/Unix Operating environment and its features. Linux/Unix commands, file structure, Regular expressions, shell features will be discussed Introduction to the features of the UNIX/LINUX operating system including text editing, text file manipulation, electronic mail, Internet utilities, directory structures, input/output handling, and shell features are part of the course curriculum CIS18A Student Learning Outcome Statements (SLO) Use the Unix/Linux Operating System utilities and shell features for basic file manipulation, networking, and communication. Course Objectives Edit text using the vi editor Maintain file and directory system Establish security and file permission, Perform basic file maintenance and use information utilities Utilize the shells Run shell commands, Implement quoting rules Communicate with email and communication utilities Apply filters and use implement basic regular expression Use basic utilities to explore system data, user data, and common tasks: exit, passwd, who, whoami, finger, w, tty, stty, uname, clear,
    [Show full text]
  • GPL-3-Free Replacements of Coreutils 1 Contents
    GPL-3-free replacements of coreutils 1 Contents 2 Coreutils GPLv2 2 3 Alternatives 3 4 uutils-coreutils ............................... 3 5 BSDutils ................................... 4 6 Busybox ................................... 5 7 Nbase .................................... 5 8 FreeBSD ................................... 6 9 Sbase and Ubase .............................. 6 10 Heirloom .................................. 7 11 Replacement: uutils-coreutils 7 12 Testing 9 13 Initial test and results 9 14 Migration 10 15 Due to the nature of Apertis and its target markets there are licensing terms that 1 16 are problematic and that forces the project to look for alternatives packages. 17 The coreutils package is good example of this situation as its license changed 18 to GPLv3 and as result Apertis cannot provide it in the target repositories and 19 images. The current solution of shipping an old version which precedes the 20 license change is not tenable in the long term, as there are no upgrades with 21 bugfixes or new features for such important package. 22 This situation leads to the search for a drop-in replacement of coreutils, which 23 need to provide compatibility with the standard GNU coreutils packages. The 24 reason behind is that many other packages rely on the tools it provides, and 25 failing to do that would lead to hard to debug failures and many custom patches 26 spread all over the archive. In this regard the strict requirement is to support 27 the features needed to boot a target image with ideally no changes in other 28 components. The features currently available in our coreutils-gplv2 fork are a 29 good approximation. 30 Besides these specific requirements, the are general ones common to any Open 31 Source Project, such as maturity and reliability.
    [Show full text]
  • Dyalog for UNIX UI Guide
    Dyalog for UNIX UI Guide Dyalog version 18.0 The tool of thought for software solutions Dyalog is a trademark of Dyalog Limited Copyright © 1982-2020 by Dyalog Limited All rights reserved. Dyalog for UNIX UI Guide Dyalog version 18.0 Document Revision: 20210429_180 Unless stated otherwise, all examples in this document assume that ⎕IO ⎕ML ← 1 No part of this publication may be reproduced in any form by any means without the prior written permission of Dyalog Limited. Dyalog Limited makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Dyalog Limited reserves the right to revise this publication without notification. email: [email protected] https://www.dyalog.com TRADEMARKS: SQAPL is copyright of Insight Systems ApS. Array Editor is copyright of davidliebtag.com Raspberry Pi is a trademark of the Raspberry Pi Foundation. Oracle®, Javascript™ and Java™ are registered trademarks of Oracle and/or its affiliates. UNIX® is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. Windows® is a registered trademark of Microsoft Corporation in the United States and other countries. macOS® and OS X® (operating system software) are trademarks of Apple Inc., registered in the U.S. and other countries. All other trademarks and copyrights are acknowledged. iii Contents Overview
    [Show full text]