《Expert Shell Scripting》：调试技巧解析与复杂代码调试策略

需积分: 3 83 浏览量更新于2024-08-01 收藏 1.56MB PDF 举报

"《Apress - Expert Shell Scripting (2010)》是一本深入探讨Shell脚本编程的专业书籍，由Ron Peters撰写，版权属于2009年。这本书并不侧重于基础的脚本编写教程，而是着重于提升脚本编写技巧和理解，其中特别强调了调试在成功脚本开发中的核心作用。在编程过程中，无论是初学者还是经验丰富的开发者，都无法避免代码中的错误。这些错误可以分为两类：语法错误和逻辑错误。语法错误通常比较容易识别，因为它们会在代码运行时抛出错误，比如拼写错误、缺少必要的标点符号或语句结构问题。然而，逻辑错误更为棘手，因为脚本可能在编译阶段没有报错，但运行结果与预期不符。这可能是由于条件判断、循环结构或者函数调用等问题导致的。书中详细讲解了如何有效地进行调试，包括但不限于使用命令行工具（如`grep`, `sed`, `awk`等）、日志记录、断点设置以及利用调试器（如`bash`内置的`set -x`选项或第三方工具）。此外，还可能涉及代码审查和重构技巧，以帮助找出隐藏的逻辑问题，并确保代码质量。作者Ron Peters在这本书中分享了他的经验和最佳实践，让读者不仅掌握Shell脚本的基础语法，还能学会如何高效地处理和解决实际编程中的挑战。书中还包含了实用的例子和练习，以便读者通过实践提升调试技能。整体而言，《Expert Shell Scripting (2010)》是一本适合想要深入学习和提高Shell编程能力的开发者和系统管理员的参考资料。"

xxi

Introduction

I learned the basics of programming when I was in school; I learned how to shell-script by

example.

I’ve met and worked with many system administrators and other *NIX folks, each of

whom has their own bag of tricks when it comes to managing a system, interacting with

their environment, or coding a script. It’s always very useful to have conversations and

interact with people like this because you invariably gain some tidbits that you can

throw into your own collection of tricks. I decided to collect all the useful shell-scripting

and interaction techniques I have learned through the years and combine them into one

beneficial reference guide. In fact, I used some of my own notes about those techniques

while writing this book. Since I haven’t memorized everything present in this book, I

would periodically look up items when I was working on various tasks. I want this book

to be the beginning of a higher-level reference library that can be added to and can grow

continually.

You might be aware of the large number of shell-scripting books and online resources

aiding in the mastery of shell scripting. Many are excellent and cover a wide range of topics.

The main purpose of this book is to combine some of the most unique tools, code snippets,

and scripts that go beyond the level of basic scripts. I wanted to create a cookbook of sorts—

lesser-known recipes and fairly advanced algorithms that have proved useful to me.

I have included scripts you can use as is, and sample scripts illustrating a specific algo-

rithm. I also demonstrate a few complex commands that may be useful on the command

line. I have tried to tailor the scripts to be useful at multiple levels. Most times, however,

there is little or no error-checking since that is not necessarily the point of a specific script.

You must be prepared to make modifications to fit your local environment.

How This Book Came About

My friend Brian Culp and I have worked together as UNIX system administrators for many

years. Periodically, Brian or I will be working on some script and run into a problem. One

of us will stop, walk over to the other, and say something like, “Do you have any code that

does X?” The answer may be no, in which case we’ll launch into a discussion on how we

might tackle the problem, or come up with a few different solutions. However, many times

it might be something like, “Hmm, yeah, I think I remember doing something like that in

a script that does X on system Y. Let me look for a minute.” A few carefully chosen grep

commands, and the solution is at hand.

xxii

■INTRODUCTION

Although finding the solution we want is great, it’s not the most efficient use of our

time. To go from having a place to store and organize all of our (and, of course, other

programmers’) gems and having them in a heavily documented form, to writing a book

on the subject was only a short step. Even though it is possible to search online references

quickly for specific code, there were many occasions when I just wanted to pull a book off

my shelf. It’s not always obvious what to search for when you have a specific itch that

needs scratching, so you’re not sure exactly to what search for online.

This is to some extent an expression of my own limitations: my family and friends think

I’m a computer guru, but rest assured, I know better. There are many programmers out

there who are much more adept at shell coding than I am. I mainly intended to collect,

order, and explain code that I have found to be highly useful in my professional experi-

ence as a system administrator, and share that information with others.

Who Should Read This Book

The book is meant for the intermediate shell coder up to the advanced shell-code hacker,

because I don’t explain many basic programming structures. If you’re looking for that

type of book, you should look to the resources mentioned in Appendix C.

This is not to say that the beginner won’t find this book useful; it may work well as a supple-

mentary reference to a more traditional shell-scripting training guide. But there is a difference

between learning English as a second language and learning how to apply sarcasm. This book

is like sarcasm in that example; it assumes some basic shell-code literacy.

I go into great detail about how and why the scripts were written in their present form,

and I include some explanation of how to avoid certain problems. Much of my learning

came from sources heavy in obfuscation and light on clarity, so I tried to be as explicit as

possible, and favored explaining too much rather than too little. You can think of many

chapters I included as shell scripts with extremely detailed commentary.

The book is divided into three parts: “Basic Scripting Techniques,” “System Interaction

and Advanced Techniques,” and “Useful Scripts.” Most chapters serve as stand-alone

discussions, although they may refer to other chapters on some minor points.

Issues and Ideas

I have made every effort to test the code that I included in this book to validate that it

works. With a project of this size, however, even with the number of eyes that have

reviewed it, there may be mistakes. I would like to know about the mistakes as well as, and

more importantly, any other ideas and scripts that could be used for future revisions of

this book. Please drop me a note at rbpeters@peterro.com.

■ ■ ■

CHAPTER 1

Shell Script Debugging

Even though this book isn’t a “how to script” manual, some concepts that are funda-

mental to writing successful scripts should be discussed. Debugging is one of them.

Debugging code is a significant part of writing code. No matter how disciplined you are

or how skilled you become at coding, you will have bugs in your code, in the form of either

syntax or logic errors. The syntactical problems tend to be simpler to resolve since many

times they show up when the code throws an error when it is run. The logical bugs, on the

other hand, may be more difficult to track down since the code may run without error, but

the resulting output does not match the design of the program. The more complex your

code becomes as your skill increases, the more difficult these types of problems will be to

detect.

Since writing bug-free code is nearly impossible, you need a few techniques up your

sleeve that will help you finish, diagnose, repair, and clean up your code. This chapter pre-

sents a few ways to debug code that I have used consistently and that help me extract

details from the inner workings of my scripts. These techniques validate that the code is

living up to my expectations and demonstrate where the code needs more work to per-

form the intended task.

Shell Trace Options

The first technique—using the set command—is the simplest to implement and can give

you great amounts of detail about how the logic is progressing and the values of variables

internal to your script. Using the set command is really just using shell options to display

verbose output when the script is running. One of the functions of the set command is to

turn on and off the various options that are available in the shell. In this case, the option

being set is -x, or xtrace. This is where the running script will, in addition to any normal

output, display the expanded commands and variables of a given line of code before the

code is run. With this increased output, you can easily view what is happening in the run-

ning script and possibly determine where your problem lies.

When you put the instruction set -x into your script, each of the commands that exe-

cute after that set instruction will be displayed, together with any arguments that were

supplied to the command, including variables and their values. Each line of output will be

剩余281页未读，继续阅读

huchaonian

粉丝: 3
资源: 4

《Expert Shell Scripting》：调试技巧解析与复杂代码调试策略

Expert Shell Scripting

Apress - Understanding Azure Data Factory.2019

Apress.Expert.Shell.Scripting

Linux/Unix系统管理员必备：《Expert Shell Scripting》深度解析

Shell脚本专家指南-中英文

Pro Vim(Apress,2014)

linux shell脚本

UNIX and Linux shell命令,shell编程资料,Per中文件手册

shell资料合集(共12本)

2009年Apress《专家Shell脚本编程》：权威指南

最新资源