blocks|key|1879806|text|malloc(3)只是一个提示，说明malloc是手册页第3部分的一部分。第3部分是库函数的位置。这是通过反对手册页的第2节中的syscall。没有malloc(2)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1879807|例如：|1879808|fwrite是一个库函数，因此有时会编写为fwrite(3)|1879809|write是一个系统调用，所以有时写成write(2)|1879810|如果您运行以下命令：|1879811|$+man+man|code-block|syntax|javascript|1879812|它会告诉你|1879813|+++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+convenâ
+++++++tions),+e.g.+man(7),+groff(7)
+++8+++System+administration+commands+(usually+only+for+root)
+++9+++Kernel+routines+[Non+standard]|1879814|entityMap^0|0|9|I|6|22|9|0|0|0|6|L|9|0|0|5|J|8|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1B|8|@$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1G|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|1H|8|@]|D|@]|E|$Q|R]]|$1|S|3|T|5|6|7|1I|8|@]|D|@]|E|$]]|$1|U|3|V|5|P|7|1J|8|@]|D|@]|E|$Q|R]]|$1|W|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]]|X|$]]

<code>malloc(3)</code> is just a hint that <code>malloc</code> is a part of the section 3 of the man pages. The section 3 is where are the library functions. This is by opposition to the section 2 of the man pages where are the syscalls. There is no <code>malloc(2)</code>.

For example:

<code>fwrite</code> is a library function so sometimes written as <code>fwrite(3)</code>

<code>write</code> is a syscall so sometimes written as <code>write(2)</code>

If you run the command:

<pre><code>$ man man
</code></pre>

it will tell you

<pre><code> 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 convenâ
 tions), e.g. man(7), groff(7)
 8 System administration commands (usually only for root)
 9 Kernel routines [Non standard]
</code></pre>

blocks|key|3290634|text|看起来作者只是非常具体而已。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3290635|如果可能存在相同函数的shell版本，则指定对手册页的第3节的引用通常很有用。例如，printf(1)与printf(3)的man+1+printf。|offset|length|style|CODE|3290636|但是对于malloc，文档应该只存在于第3节中。|3290637|entityMap^0|0|1Q|C|0|4|6|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

It looks like the author is simply being very specific.

Specifying the reference to section 3 of the man pages is often useful if there might be an e.g. shell version of the same function. For instance, <code>man 1 printf</code> for printf(1) vs. printf(3).

But in the case of <code>malloc</code> documentation should exist only in section 3.

blocks|key|1880341|text|前言:我的unix很弱。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1880342|我相信这只是对第三节库的引用。|1880343|(摘自行话文件)|1880344|诸如malloc(3)和patch(1)之类的引用是针对Unix工具的(其中一些工具，例如patch(1)，实际上是通过Usenet分发的开源工具)。|1880345|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Preface: My unix is weak.

I believe that it is simply a reference to the section 3 library.

( from the jargon file ) 
References such as malloc(3) and patch(1) are to Unix facilities (some of which, such as patch(1), are actually open source distributed over Usenet).

While reading a <a href="http://www.phrack.org/issues.html?issue=68&amp;id=10" rel="nofollow">hacker article</a> on the jemalloc memory manager, the hacker keeps referring to malloc(3), not malloc. I wondered why. 

Does he do so because it refers to a specific linux malloc implementation? Or simply to refer to all malloc variants, that implement the interface as described on the <a href="http://linux.die.net/man/3/malloc" rel="nofollow">section 3 (libary functions)</a> of the unix/linux manual pages? This option is my guess, want to be sure. Is there a different reason? 

So, is the hacker just overly specific? Or is there a difference between malloc and malloc(3)?

The (3) part is not a reference to other documentation, article or research mentioned later in the hacker article.

What is the difference between malloc and malloc(3)?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在jemalloc内存管理器上读取时，黑客总是引用malloc(3)，而不是malloc。我想知道为什么。他这样做是因为它引用了特定的linux malloc实现吗？或者只是简单地引用所有的malloc变体，它们实现了unix/linux手册页的中描述的接口？这个选项是我的猜测，我想确认一下。还有其他原因吗？那么，黑客...

问malloc和malloc(3)的区别是什么？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问malloc和malloc(3)的区别是什么？EN