> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/man/pthread/pthread_key_delete.3.md).

# pthread\_key\_delete.3

`pthread_key_delete` — 删除线程特定数据键

## 名称

`pthread_key_delete`

## 库

libpthread

## 概要

```c
#include <pthread.h>

int
pthread_key_delete(pthread_key_t key);
```

## 描述

`pthread_key_delete` 函数删除先前由 [pthread\_key\_create(3)](/man/pthread/pthread_key_create.3.md) 返回的线程特定数据键。在调用 `pthread_key_delete` 时，与 `key` 关联的线程特定数据值不必为 NULL。应用程序有责任释放任何应用存储，或对与被删除的键或任何线程中关联的线程特定数据相关的数据结构执行任何清理操作；这种清理可以在调用 `pthread_key_delete` 之前或之后进行。在调用 `pthread_key_delete` 之后任何试图使用 `key` 的行为都将导致未定义行为。

`pthread_key_delete` 函数可从析构函数中调用。`pthread_key_delete` 不会调用析构函数。先前可能与 `key` 关联的任何析构函数将不再在线程退出时被调用。

## 返回值

如果成功，`pthread_key_delete` 函数将返回零；否则将返回一个错误号以指示错误。

## 错误

`pthread_key_delete` 函数将在以下情况失败：

**`[EINVAL]`** `key` 值无效。

## 参见

[pthread\_getspecific(3)](/man/pthread/pthread_getspecific.3.md), [pthread\_key\_create(3)](/man/pthread/pthread_key_create.3.md), [pthread\_setspecific(3)](/man/pthread/pthread_setspecific.3.md)

## 标准

`pthread_key_delete` 函数符合 ISO/IEC 9945-1:1996 ("POSIX.1") 规范。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://book.bsdcn.org/man/pthread/pthread_key_delete.3.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.