> For the complete documentation index, see [llms.txt](https://freebsd-journal-cn.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://freebsd-journal-cn.bsdcn.org/20190304-tiao-shi-yu-ce-shi/letter-from-the-foundation.md).

# 基金会来信

北半球大部分地区春意盎然，而在春天，年轻开发者的心思也会转向调试和测试。如果你对此存疑，那么本期刊登的三篇精彩文章足以让你改观。

作为佐证，我们奉上：John Baldwin 的《Debugging with GDB》、Kristof Provost 的《The Automated Testing Framework》、Benedict Reuschling 的《Diagnosing Excess LDAP Connections Using DTrace》。虽然许多开发者仍在用 `printf()` 调试，但你不必继续这样过活——John Baldwin 带我们领略了 GNU 调试器 gdb 最新版本（8.3）的功能，并展示了它如何为我们节省数小时追踪 bug 的挫败时间。

防止代码出 bug 的最佳手段是好的测试，这正是 Kristof Provost 在文章中向我们阐述的内容。三篇中的第三篇是 Benedict Reuschling 的实践经历文章，讲述在运行中的系统上用 DTrace 调试问题。

本期春季刊还带来了全新的专栏阵容。Dru Lavigne 介绍了新 Ports 提交者 Kai Knoblich；Michael W Lucas 回答了一些读者来信；Steven Kreuzer 在 SVN 动态中向我们介绍源代码树中的最新动态。FreeBSD 基金会执行董事 Deb Goodkin 带来了 FOSDEM 报告——这是 2019 年首场大型开源会议，吸引了来自欧洲和世界各地逾 5000 名开源项目参与者，在比利时度过一个周末的会议、演讲和聚会。说到会议，如果你有兴趣参加 FreeBSD 相关活动，可以在由 Dru Lavigne 和 Anne Dickison 整理的活动日历中找到清单。

我们期待在 5 月中旬于加拿大安大略省渥太华举办的 BSDCan 上见到尽可能多的读者。大多数编辑委员会成员都会到场，如果你在那里看到我们，请停下来打个招呼，告诉我们 FreeBSD 期刊做得如何。

**GEORGE NEVILLE-NEIL**


---

# 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://freebsd-journal-cn.bsdcn.org/20190304-tiao-shi-yu-ce-shi/letter-from-the-foundation.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.