零基础入门：Linux下Assembly语言编程指南

5星 · 超过95%的资源需积分: 0 64 浏览量更新于2024-07-29 收藏 30.66MB PDF 举报

《Linux汇编语言编程指南》是一本面向初学者的Linux编程入门书籍，作者是Sivarama P. Dandamudi，他来自加拿大Carleton大学的计算机科学学院。这本书的独特之处在于它无需读者具备任何计算机语言基础或Linux编程经验，即使是Linux新手也能轻松理解和上手。作者以通俗易懂的方式讲解了Assembly语言在Linux环境中的应用，旨在帮助读者建立起从零开始学习Linux编程的基础。书中涵盖了以下核心知识点： 1. **Linux系统基础**：首先，读者将被引导理解Linux操作系统的概念，包括文件系统、进程管理、内存管理等基础知识，这对于后续的汇编语言编程至关重要。 2. **Assembly语言基础**：从最基本的指令集开始，如数据类型、运算符、控制结构等，逐步介绍Assembly语言的语法和逻辑。读者会了解到如何使用Assembly语言与底层硬件进行直接交互。 3. **汇编语言编程入门**：通过实际项目演示，如编写简单的系统调用、处理中断、实现循环和条件判断等，让读者掌握基本的程序设计技巧。 4. **Linux汇编接口**：学习如何利用Linux提供的系统调用接口，以及如何与C库和其他系统工具配合，以提高编程效率。 5. **性能优化与调试**：书中还会涉及汇编语言性能优化的方法，以及如何使用调试工具来跟踪和解决问题。 6. **版权与使用许可**：最后，关于版权的法律注意事项被明确指出，强调了在使用电子资源时的合法合规性，确保遵循Springer Science+Business Media的出版规定。《Linux汇编语言编程指南》不仅适合那些想要深入了解操作系统底层机制的程序员，也适合对计算机科学感兴趣的爱好者，无论他们之前是否有编程经验。这是一本循序渐进、实用性强的教程，有助于读者快速进入Linux汇编编程的世界。

Assembly Language

The

main objective

this chapter is to give

you

brief

introduction

the

assembly

language.

achieve this

goal,

compare and contrast the

assembly

language

with

high-level languages

you

are familiar

with.

This

comparison enables

us to

take a

look

at the pros and cons

the

assembly

language vis-a-vis high-level

languages.

Introduction

A user's view of a computer system depends on the degree of abstraction provided by the under-

lying software. Figure 1.1 shows a hierarchy of levels at which one can interact with a computer

system. Moving to the top of the hierarchy shields the user from the lower-level details. At the

highest level, the user interaction is limited to the interface provided by application software such

as spreadsheet, word processor, and so on. The user is expected to have only a rudimentary knowl-

edge of how the system operates. Problem solving at this level, for example, involves composing

a letter using the word processor software.

At the next level, problem solving is done in one of the

high-level languages

such as C and

Java. A user interacting with the system at this level should have detailed knowledge of software

development. Typically, these users are application

programmers.

Level

users

are

knowledgeable

about the application and the high-level language that they would use to write the application

software. They may not, however, know internal details of the system unless they also happen to

be involved in developing system software such as device drivers, assemblers, linkers, and so on.

Both levels 4 and 5 are

system

independent,

that is, independent of

particular processor used

in the system. For example, an application program written in C can be executed on a system with

an Intel processor or a PowerPC processor without modifying the source code. All we have to

do is recompile the program with a C compiler native to the target system. In contrast, software

development done at all levels below level 4 is

system

dependent.

Assembly language programming is referred to as

low-level programming

because each as-

sembly language instruction performs a much lower-level task compared to an instruction in a

high-level language. As a consequence, to perform the same task, assembly language code tends

to be much larger than the equivalent high-level language code.

Assembly language instructions are native to the processor used in the system. For example,

a program written in the Intel assembly language cannot be executed on the PowerPC processor.

Chapter

• Assembly Language

Even though assembly language is considered a low-level language, programming in assembly

language will not expose you to all the nuts and bolts of the system. Our operating system hides

several of the low-level details so that the assembly language programmer can breathe easy. For

example, if we want to read input from the keyboard, we can rely on the services provided by the

operating system.

Well, ultimately there has to be something to execute the machine language instructions. This

is the system hardware, which consists of digital logic circuits and the associated support elec-

tronics. A detailed discussion of this topic is beyond the scope of this book. Books on computer

organization discuss this topic in detail.

What Is Assembly Language?

Assembly language is directly influenced by the instruction set and architecture of the processor.

In this book, we focus on the assembly language for the Intel 32-bit processors like the Pentium.

The assembly language code must be processed by a program in order to generate the machine

language code. Assembler is the program that translates the assembly language code into the

machine language.

NASM (Netwide Assembler), MASM (Microsoft Assembler), and TASM (Borland Turbo As-

sembler) are some of the popular assemblers for the Intel processors. In this book, we use the

NASM assembler. There are two main reasons for this selection: (i) It is a free assembler; and

(ii) NASM supports a variety of formats including the formats used by Microsoft

Windows,

Linux

and a host of others.

Are you curious as to how the assembly language instructions look like? Here are some exam-

ples:

inc result

mov class_size,45

and

maskl,12 8

add marks,10

The first instruction increments the variable result. This assembly language instruction is equiv-

alent to

result++;

in C. The second instruction initializes class_size to

45.

The equivalent statement in C is

class_size = 45;

The third instruction performs the bitwise and operation on ma ski and can be expressed in C as

maskl = maskl & 128/

The last instruction updates marks by adding 10. In C, this is equivalent to

marks = marks + 10/

These examples illustrate several points:

Assembly Language Programming in Linux

Assembly language instructions are cryptic.

Assembly language operations are expressed by using mnemonics (like and and inc).

Assembly language instructions are low level. For example, we cannot write the following

in the assembly language:

add marks,value

This instruction is invalid because two variables, marks and value, are not allowed in a

single instruction.

We appreciate the readability of the assembly language instructions by looking at the equiva-

lent machine language instructions. Here are some machine language examples:

Assembly language Operation Machine language (in hex)

nop

operation

9 0

inc result Increment FF060A00

mov class_size,45 Copy C7060C002D00

and mask, 128 Logical and 80260E0080

add marks, 10 Integer addition 83060F000A

In the above table, machine language instructions are written in the hexadecimal number sys-

tem. If you are not familiar with this number system, see Appendix A for

quick review of number

systems.

It is obvious from these examples that understanding the code of a program in the machine

language is almost impossible. Since there is a one-to-one correspondence between the instruc-

tions of the assembly language and the machine language, it is fairly straightforward to translate

instructions from the assembly language to the machine language. As a result, only a masochist

would consider programming in a machine language. However, life was not so easy for some of

the early progranmiers. When microprocessors were first introduced, some programming was in

fact done in machine language!

Advantages of High-Level Languages

High-level languages are preferred to program applications, as they provide a convenient abstrac-

tion of

the

underlying system suitable for problem solving. Here are some advantages of program-

ming in a high-level language:

Program development

faster.

Many high-level languages provide structures (sequential, selection, iterative) that facilitate

program development. Programs written in a high-level language are relatively small com-

pared to the equivalent programs written in an assembly language. These programs are also

easier to code and debug.

Programs are

easier to

maintain.

Programming a new application can take from several weeks to several months and the

lifecycle of such an application software can be several years. Therefore, it is critical that

software development be done with a view of software maintainability, which involves ac-

tivities ranging from fixing bugs to generating the next version of the software. Programs

Chapter

• Assembly Language

written in

high-level language are easier to understand and, when good programming prac-

tices are followed, easier to maintain. Assembly language programs tend to be lengthy and

take more time to code and debug. As a result, they are also difficult to maintain.

Prog

rams

portable,

High-level language programs contain very few processor-specific details. As a result, they

can be used with little or no modification on different computer

systems.

In contrast, assem-

bly language programs are processor-specific.

Why Program in Assembly Language?

The previous section gives enough reasons to discourage you from programming in the assem-

bly language. However, there are two main reasons why programming is still done in assembly

language: (i) efficiency, and (ii) accessibility to system hardware.

Efficiency

refers to how "good" a program is in achieving a given objective. Here we consider

two objectives based on space (space-efficiency) and time (time-efficiency).

Space-efficiency

refers to the memory requirements of a program, that is, the size of the ex-

ecutable code. Program A is said to be more space-efficient if it takes less memory space than

program

to perform the same task. Very often, programs written in the assembly language tend

to be more compact than those written in a high-level language.

Time-efficiency

refers to the time taken to execute a program. Obviously a program that runs

faster is said to be better from the time-efficiency point of view. If we craft assembly language

programs carefully, they tend to run faster than their high-level language counterparts.

As an aside, we can also define a third objective: how fast a program can be developed (i.e.,

write code and debug). This objective is related to the

programmer

productivity,

and assembly

language loses the battle to high-level languages as discussed in the last section.

The superiority of assembly language in generating compact code is becoming increasingly

less important for several reasons. First, the savings in space pertain only to the program code

and not to its data space. Thus, depending on the application, the savings in space obtained by

converting an application program from some high-level language to the assembly language may

not be substantial. Second, the cost of memory has been decreasing and memory capacity has

been increasing. Thus, the size of a program is not a major hurdle anymore. Finally, compil-

ers are becoming "smarter" in generating code that is both space- and time-efficient. However,

there are systems such as embedded controllers and handheld devices in which space-efficiency is

important.

One of the main reasons for writing programs in an assembly language is to generate code

that is time-efficient. The superiority of assembly language programs in producing efficient code

is a direct manifestation of

specificity.

That is, assembly language programs contain only the

code that is necessary to perform the given task. Even here, a "smart" compiler can optimize the

code that can compete well with its equivalent written in the assembly language. Although the

gap is narrowing with improvements in compiler technology, assembly language still retains its

advantage for now.

The other main reason for writing assembly language programs is to have direct control over

system hardware. High-level languages, on purpose, provide a restricted (abstract) view of the

underlying hardware. Because of

this,

it is almost impossible to perform certain tasks that require

access to the system hardware. For example, writing a device driver for a new scanner on the

market almost certainly requires programming in assembly language. Since assembly language

剩余538页未读，继续阅读

qianfeng_linux

粉丝: 0
资源: 1

零基础入门：Linux下Assembly语言编程指南

Guide to Assemblly Language Programming in Linux

基于对知乎热榜话题的数据抓取分析与可视化python实现源码+文档说明（高分完整项目）

电子技术课程 电路分析技术 12 非正弦周期电流电路及电路频率特性 共43页.pptx

(完整数据)全国及各省森林覆盖率、森林面积，700个城市绿地面积、绿化率等数据

公司面试题记录汇总11

【教程4＞第2章＞第21节】软解调讲解2——FPGA开发,以16QAM为例_16qam软解调算法实现-CSDN博客.pdf

整理本人在2021年10月-12月期间写的一些爬虫演示，比如用于渗透测试中SQL注入的URL收集脚本（爬取必应和百度搜索结果的URL），子授权爆破演示，大型高校漏洞信息收集爬虫，以及入门爬虫时.zip

无线网络渗透测试WPA,WPA2密码还原.zip

Image_93236610692.jpg

【java毕业设计】高校科研管理系统源码（完整前后端+说明文档+LW）.zip

最新资源

电子技术课程电路分析技术 12 非正弦周期电流电路及电路频率特性共43页.pptx