2010-07-08 22:03:41 +04:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2017-10-01 14:21:40 +03:00
< html xmlns = "http://www.w3.org/1999/xhtml" lang = "zh-CN" xml:lang = "zh-CN" >
2010-07-08 22:03:41 +04:00
< head >
<!--
*
2020-03-31 09:05:33 +03:00
* Copyright 2008-2020, Haiku. All rights reserved.
2010-07-08 22:03:41 +04:00
* Distributed under the terms of the MIT License.
*
* Authors:
2010-08-11 21:56:45 +04:00
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
2010-07-08 22:03:41 +04:00
* Humdinger < humdingerb @ gmail . com >
2010-08-02 20:51:09 +04:00
* Translators:
2010-09-17 17:28:39 +04:00
* dgy18787
2018-09-26 08:46:30 +03:00
* Pengphei Han
2021-07-21 10:51:26 +03:00
* Máximo Castañeda
2010-07-08 22:03:41 +04:00
*
-->
< meta http-equiv = "content-type" content = "text/html; charset=utf-8" / >
< meta name = "robots" content = "all" / >
2010-08-02 20:51:09 +04:00
< title > 报告错误< / title >
2017-10-01 14:21:40 +03:00
< meta name = "viewport" content = "width=device-width, initial-scale=1.0" / >
2010-07-08 22:03:41 +04:00
< link rel = "stylesheet" type = "text/css" href = "../Haiku-doc.css" / >
< / head >
< body >
< div id = "banner" >
2010-10-28 12:57:17 +04:00
< div > < span > 用户指南< / span > < / div >
2010-07-08 22:03:41 +04:00
< / div >
< div class = "nav" >
< div class = "inner" >
< ul class = "lang-menu" >
2020-03-31 09:05:33 +03:00
< li class = "now" > 中文 ［中文］ < span class = "dropdown-caret" > ▼ < / span > < / li >
< li > < a href = "../id/bugreports.html" > Bahasa Indonesia< / a > < / li >
< li > < a href = "../ca/bugreports.html" > Català< / a > < / li >
< li > < a href = "../de/bugreports.html" > Deutsch< / a > < / li >
< li > < a href = "../en/bugreports.html" > English< / a > < / li >
< li > < a href = "../es/bugreports.html" > Español< / a > < / li >
2021-07-21 10:51:26 +03:00
< li > < a href = "../eo/bugreports.html" > Esperanto< / a > < / li >
2020-03-31 09:05:33 +03:00
< li > < a href = "../fr/bugreports.html" > Français< / a > < / li >
< li > < a href = "../fur/bugreports.html" > Furlan< / a > < / li >
< li > < a href = "../it/bugreports.html" > Italiano< / a > < / li >
< li > < a href = "../hu/bugreports.html" > Magyar< / a > < / li >
< li > < a href = "../pl/bugreports.html" > Polski< / a > < / li >
< li > < a href = "../pt_PT/bugreports.html" > Português< / a > < / li >
< li > < a href = "../pt_BR/bugreports.html" > Português (Brazil)< / a > < / li >
< li > < a href = "../ro/bugreports.html" > Română< / a > < / li >
< li > < a href = "../sk/bugreports.html" > Slovenčina< / a > < / li >
< li > < a href = "../fi/bugreports.html" > Suomi< / a > < / li >
< li > < a href = "../sv_SE/bugreports.html" > Svenska< / a > < / li >
< li > < a href = "../tr/bugreports.html" > Türkçe< / a > < / li >
< li > < a href = "../ru/bugreports.html" > Русский< / a > < / li >
< li > < a href = "../uk/bugreports.html" > Українська< / a > < / li >
< li > < a href = "../jp/bugreports.html" > 日本語< / a > < / li >
2010-07-08 22:03:41 +04:00
< / ul >
< span >
< a href = "../welcome_zh_CN.html" class = "uplink" > Welcome< / a >
< / span > < / div >
< / div >
< div id = "content" >
< div >
2014-04-05 20:48:32 +04:00
< div class = "box-info" > 本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。< / div >
2010-08-11 21:56:45 +04:00
< table class = "index" id = "index" summary = "index" >
2012-08-18 12:28:04 +04:00
< tr class = "heading" > < td > 索引< / td > < / tr >
2010-09-17 17:28:39 +04:00
< tr class = "index" > < td > < a href = "#account" > 获取Trac账户< / a > < br / >
< a href = "#report" > 创建错误报告< / a > < br / >
< a href = "#app" > 软件错误< / a > < br / >
< a href = "#server" > 服务错误< / a > < br / >
< a href = "#kernel" > 内核错误< / a > < br / >
< a href = "#kdl" > 内核调试- KDL< / a > < br / >
< a href = "#syslog" > 系统日志< / a > < br / >
< a href = "#onscreen" > 屏幕调试< / a > < br / >
< a href = "#hardware" > 硬件错误< / a > < br / >
< a href = "#next" > 下一步？< / a > < / td > < / tr >
2010-08-11 21:56:45 +04:00
< / table >
2010-07-08 22:03:41 +04:00
2010-08-02 20:51:09 +04:00
< h1 > 报告错误< / h1 >
2010-07-08 22:03:41 +04:00
2010-09-17 17:28:39 +04:00
< p > 由于我们的开发人员不可能测试每种硬件组合和每种不同的系统交互方式， ， ， < / p >
2010-08-02 20:51:09 +04:00
< p > 为了确保我们的错误跟踪系统的有效性，遵守共同的< a href = "http://dev.haiku-os.org/wiki/BugTrackerEtiquette" > 错误报告规范< / a > 是很有必要的。< / p >
2010-07-08 22:03:41 +04:00
2010-08-11 21:56:45 +04:00
< h2 > < a href = "#" > < img src = "../images/up.png" style = "border:none;float:right" alt = "index" / > < / a >
2010-09-17 17:28:39 +04:00
< a id = "account" name = "accout" > 获取Trac账户< / a > < / h2 >
2014-05-31 02:02:36 +04:00
< p > 为了提交任务单，您需要在< a href = "http://dev.haiku-os.org/register" title = "Register at Haiku's Bugtracker" > Haiku 的错误跟踪系统< / a > 中注册一个账户。
2010-08-02 20:51:09 +04:00
< br / >
2010-09-17 17:28:39 +04:00
新建账户时，您需要< b > 提供自己的电子邮箱< / b > ，否则您将不具备基本的任务单修改权限。完成之后，您必须要保证< b > 检查您的垃圾邮箱< / b > ，因为所有重要的验证邮件可能都会被发送到那里。< / p >
2010-07-08 22:03:41 +04:00
2010-08-11 21:56:45 +04:00
< h2 > < a href = "#" > < img src = "../images/up.png" style = "border:none;float:right" alt = "index" / > < / a >
2010-09-17 17:28:39 +04:00
< a id = "report" name = "report" > 创建错误报告< / a > < / h2 >
2010-08-02 20:51:09 +04:00
< p > 在报告一个错误之前，请您< a href = "http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority" > 确保< / a > 该错误报告之前不存在。你可以使用< a href = "http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on" > 查找< / a > 功能来查找其是否存在。
< br / >
在确定它是一个独特的错误之后，您需要尽可能的找出有关的详细信息：< / p >
2010-07-08 22:03:41 +04:00
< ul >
2021-07-21 10:51:26 +03:00
< li > < p > 尝试在当前版本的Haiku系统中重现您的问题。 有许多用于测试的预编译镜像都是< a href = "http://download.haiku-os.org" > 可用的< / a > 。< / p > < / li >
2014-05-31 02:02:36 +04:00
< li > < p > 包括基本的信息，例如以何种方式测试 Haiku（ ， ， ） < / p > < / li >
2018-09-26 08:46:30 +03:00
< li > < p > Mention which revision you are running. You can find this information in < span class = "menu" > About Haiku...< / span > from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). The downloadable images are named accordingly, for a self-built image you should know how you built it.< / p > < / li >
2010-09-17 17:28:39 +04:00
< li > < p > 描述您所遇到的问题。尽量把问题讲得精确和明白：详细的描述系统的行为反馈，和您期望的反馈。< / p > < / li >
< li > < p > 描述出现该错误所需要的操作步骤。这将会有助于开发者重现该错误，并对其进行修复和完善。< / p > < / li >
< li > < p > 附带你所掌握的尽可能多的信息。如果是一个GUI错误， ， < span class = "key" > PRINT< / span > 键来截取当时的屏幕图像。< / p > < / li >
2010-07-08 22:03:41 +04:00
< / ul >
2010-08-11 21:56:45 +04:00
< h2 > < a href = "#" > < img src = "../images/up.png" style = "border:none;float:right" alt = "index" / > < / a >
2010-09-17 17:28:39 +04:00
< a id = "app" name = "app" > 程序错误< / a > < / h2 >
2018-09-26 08:46:30 +03:00
< p > When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the < a href = "../../userguide/zh_CN/applications/debugger.html" > Debugger< / a > .< / p >
2020-03-31 09:05:33 +03:00
< p > If it's not a crashing bug, you may get useful information when starting the application from Terminal. Some applications provide logging and other options when started with certain parameters; try < tt > -h< / tt > or < tt > --help< / tt > to see if that is the case. As example, see the different logging levels of < a href = "../../userguide/zh_CN/applications/haikudepot.html#logs" > HaikuDepot< / a > .< / p >
2010-07-08 22:03:41 +04:00
2010-08-11 21:56:45 +04:00
< h2 > < a href = "#" > < img src = "../images/up.png" style = "border:none;float:right" alt = "index" / > < / a >
2010-09-17 17:28:39 +04:00
< a id = "server" name = "server" > 服务错误< / a > < / h2 >
2018-09-26 08:46:30 +03:00
< p > When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.< br / >
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (< span class = "cli" > bt< / span > command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.< br / >
Depending on what exactly crashed, you can try to save a crash report on the Desktop with < span class = "cli" > save-report< / span > or < span class = "cli" > write-core< / span > for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands < span class = "cli" > shutdown< / span > and < span class = "cli" > reboot< / span > .< / p >
2010-07-08 22:03:41 +04:00
2010-08-11 21:56:45 +04:00
< h2 > < a href = "#" > < img src = "../images/up.png" style = "border:none;float:right" alt = "index" / > < / a >
2010-09-17 17:28:39 +04:00
< a id = "kernel" name = "kernel" > 内核错误< / a > < / h2 >
< p > 内核错误通常都是危害效果最大的错误，同时也是最难调试的错误。下面几种情形，通常都可能是内核或者驱动问题：< / p >
2010-07-08 22:03:41 +04:00
< ul >
2010-09-17 17:28:39 +04:00
< li > < p > 系统自动进入了内核调试状态（ ） ， ， < i > Welcome to Kernel Debugging Land...< / i > ”，而第一行则声明了进入内核调试状态的实时原因。< / p > < / li >
< li > < p > 系统自动重新启动。< / p > < / li >
< li > < p > 系统完全冻结。您无法移动鼠标，并且屏幕中无任何程序显示。在此情况下，重要的是测试能否使用快捷键 < span class = "key" > ALT< / span > < span class = "key" > SysReq< / span > < span class = "key" > D< / span > 进入内核调试状态（在多数键盘上，< span class = "key" > SysReq< / span > 是 < span class = "key" > PRINT< / span > 键）。然后等待至少一分钟，查看系统反应状态。< / p > < / li >
< li > < p > 系统无法实现正确引导。它可能自动重启，或停止在某个步骤（例如，某个启动图标）。对于后一种情况，可以尝试使用快捷键 < span class = "key" > ALT< / span > < span class = "key" > SysReq< / span > < span class = "key" > D< / span > 。< / p > < / li >
< li > < p > 整个系统或者部分硬件无法正确运行。例如， ， ， ， （ ， ） < / p > < / li >
2010-07-08 22:03:41 +04:00
< / ul >
2021-07-21 10:51:26 +03:00
< p > 需要注意的是，只有最后这种情况与硬件相关，而所有其他的问题也可能由硬件驱动中的错误引起。如果您对引起该问题的硬件或相关的驱动有所疑问，您可以检查删除/禁用该硬件或驱动是否会产生影响。例如，如果您怀疑无线网络有问题，您会发现 BIOS 中有可禁用它的选项。如果其中没有该选项，您可以从安装的 Haiku 中删除相关的无线网络驱动（参见 < a href = "../../../userguide/zh_CN/bootloader.html" > 引导程序< / a > ）。< / p >
2010-08-11 21:56:45 +04:00
< h3 > < a href = "#" > < img src = "../images/up.png" style = "border:none;float:right" alt = "index" / > < / a >
2010-09-17 17:28:39 +04:00
< a id = "kdl" name = "kdl" > 内核调试 - KDL< / a > < / h3 >
2018-09-26 08:46:30 +03:00
< p > If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut < span class = "key" > ALT< / span > < span class = "key" > SysReq< / span > < span class = "key" > D< / span > (< span class = "key" > SysReq< / span > being the < span class = "key" > Print< / span > key, normally).< br / >
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.< / p >
2014-05-31 02:02:36 +04:00
< p > KDL 本身是 shell 中的一类。它可以执行命令，打印系统信息。下面是一些感兴趣的命令：< / p >
2010-08-11 21:56:45 +04:00
< table summary = "layout" border = "0" cellpadding = "2" cellspacing = "0" >
2018-10-20 23:28:58 +03:00
< tr > < td > < span class = "cli" > bt< / span > (等同 < span class = "cli" > sc< / span > )< / td > < td > < / td > < td > 打印回溯信息（ ） < / td > < / tr >
2010-09-17 17:28:39 +04:00
< tr > < td > < span class = "cli" > ints< / span > < / td > < td > < / td > < td > 显示已处理和未处理的硬件中断。< / td > < / tr >
< tr > < td class = "onelinetop" > < span class = "cli" > co< / span > (aka continue)< / td > < td > < / td > < td > 离开内核调试状态；如果可能的话，继续正常的系统操作。< / td > < / tr >
< tr > < td > < span class = "cli" > reboot< / span > < / td > < td > < / td > < td > 立即重启系统。您将会丢失所有未保存的数据，甚至包括那些已经保存，但是还未写入硬盘的数据。< / td > < / tr >
2010-08-11 21:56:45 +04:00
< / table >
2010-09-17 17:28:39 +04:00
< p > 获取更多信息，请参阅 < a href = "http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land" > 欢迎使用内核调试工具< / a > 。< / p >
< p > KDL输出信息将会写入到串行端口（ ， ） ， ， ， （ ） < / p >
2012-08-18 12:28:04 +04:00
< p > 您可以从KDL输出中生成 QR 代码，而它们可以通过智能手机或相似设备转换为文本内容。有关如何使用该功能从 KDL 获取数据，详情参考 < a href = "http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output" > QR Encode your KDL Output< / a > 。< / p >
2010-08-11 21:56:45 +04:00
< h3 > < a href = "#" > < img src = "../images/up.png" style = "border:none;float:right" alt = "index" / > < / a >
2010-09-17 17:28:39 +04:00
< a id = "syslog" name = "syslog" > 系统日志< / a > < / h3 >
2014-05-31 02:02:36 +04:00
< p > < b > 这是从无法引导的系统中获取信息的首选方法。< / b >
< br / >
系统日志（ ， < span class = "path" > /boot/system/var/log/syslog< / span > 。由于写入文件需要系统处于运行状态，因此当内核出现问题时（尤其是，系统自动重启，或者无法持续 KDL 会话），最新的输出信息可能无法写入日志文件。< / p >
2018-09-26 08:46:30 +03:00
< p > 引导程序的 < span class = "menu" > Debug menu< / span > 中的< span class = "menu" > Enable debug syslog< / span > 选项可以使系统日志持久存在。如果启用了引导菜单中的 < span class = "menu" > Save syslog from previous session during boot< / span > 选项（默认情况下启用），您可以在 < span class = "path" > /boot/system/var/log/previous_syslog< / span > 中找到最近登陆会话的系统日志。< br / >
如果您无法启动并获取最近的日志文件 previous_syslog， < span class = "key" > SHIFT< / span > 进入引导程序菜单。< br / >
在引导程序的 < span class = "menu" > Debug menu< / span > 中，您可以找到 < span class = "menu" > Display syslog from previous session< / span > 和 < span class = "menu" > Save syslog from previous session< / span > 两个入口。前者将系统日志显示于屏幕，后者允许您将其保存到硬盘。需要注意的是，目前只有 FAT32 卷支持保存该文件。如果您使用 USB 磁盘，但是插入晚了，可能它将不被识别；您可以重置机器，然后再次进入引导程序菜单。但是还要注意：不要无故的启动任何操作系统，否则数据将会丢失。< / p >
2010-08-11 21:56:45 +04:00
< h3 > < a href = "#" > < img src = "../images/up.png" style = "border:none;float:right" alt = "index" / > < / a >
2010-09-17 17:28:39 +04:00
< a id = "onscreen" name = "onscreen" > 屏幕调试< / a > < / h3 >
2018-09-26 08:46:30 +03:00
< p > < b > 屏幕调试输出仅对调试特殊问题有用，而且自身也有（定时）问题。若非必须，不要使用它。< / b > < br / >
只有当 Haiku 引导机器失败，而且 < span class = "menu" > Debug syslog option< / span > 出于某些原因无法使用，它才具有重要意义。 在Haiku的引导徽标出现之前， < span class = "key" > SHIFT< / span > 进入引导程序菜单。 选择 < span class = "menu" > Select safe mode options< / span > 。 在接近屏幕底部，< span class = "menu" > [ ] Enable on screen debug output< / span > 将会列出。（ ： ， < br / >
最后，选择 < span class = "menu" > Return to main menu< / span > 和 < span class = "menu" > Continue booting< / span > 。< br / >
在屏幕上将会显示一页或者多页文本，只有最后几行才需要附带到您的错误报告。更多信息，参阅 < a href = "../../userguide/zh_CN/bootloader.html" > 引导程序< / a > 。< / p >
2010-08-11 21:56:45 +04:00
< h2 > < a href = "#" > < img src = "../images/up.png" style = "border:none;float:right" alt = "index" / > < / a >
2010-09-17 17:28:39 +04:00
< a id = "hardware" name = "hardware" > 硬件错误< / a > < / h2 >
< p > 在处理有关硬件/驱动的问题时，您需要在报告中附带下面的信息：< / p >
2010-08-11 21:56:45 +04:00
< table summary = "layout" border = "0" cellpadding = "2" cellspacing = "0" >
2010-09-17 17:28:39 +04:00
< tr > < td > - < span class = "cli" > listdev< / span > < / td > < td > < / td > < td > 给出所有硬件的详细列表，包括提供商和 PCI ID； < span class = "cli" > lshw< / span > 和 < span class = "cli" > lspci< / span > 。< / td > < / tr >
< tr > < td > - < span class = "cli" > listusb -v< / span > < / td > < td > < / td > < td > 假如是有关 USB 的问题， < span class = "cli" > lsusb< / span > 。< / td > < / tr >
2018-10-20 23:28:58 +03:00
< tr > < td > - < span class = "cli" > open /var/log/syslog< / span > < / td > < td > < / td > < td > Haiku的主要系统日志， < a href = "#syslog" > Syslog< / a > ，类似于引导过程中的屏幕调试信息。您可以使用 < span class = "cli" > open< / span > 命令在文本编辑器中获取到系统日志中相关的部分。< / td > < / tr >
2010-09-17 17:28:39 +04:00
< tr > < td class = "onelinetop" > - < span class = "cli" > listimage | grep drivers/< / span > < / td > < td > < / td > < td > 列出所有使用的驱动。< / td > < / tr >
2019-10-20 00:22:44 +03:00
< tr > < td > - < span class = "cli" > usb_hid_report< / span > < / td > < td > < / td > < td > In case of USB input devices, add the < span class = "cli" > /tmp/usb_hid_report_descriptor_*.bin< / span > file.< / td > < / tr >
2010-09-17 17:28:39 +04:00
< tr > < td > - < span class = "cli" > ints< / span > < / td > < td > < / td > < td > 只在 < i > 内核调试状态< / i > 可用（参阅下文）。它用显示中断使用情况。不可能有许多由不同硬件共享的中断。< / td > < / tr >
2018-10-20 23:28:58 +03:00
< tr > < td colspan = "3" > - 屏幕调试输出（一种安全模式引导时间选项，查看 < a href = "#onscreen" > 上述< / a > ）。< / td > < / tr >
2010-08-11 21:56:45 +04:00
< / table >
2010-09-17 17:28:39 +04:00
< p > 前四个命令需要在终端中进行输入。在命令后添加 < span class = "cli" > > output.txt< / span > ， ， < / p >
2010-07-08 22:03:41 +04:00
2010-08-11 21:56:45 +04:00
< h2 > < a href = "#" > < img src = "../images/up.png" style = "border:none;float:right" alt = "index" / > < / a >
2010-09-17 17:28:39 +04:00
< a id = "next" name = "next" > 下一步< / a > < / h2 >
< p > 在您提交错误报告之后，开发人员将会检查您的错误，然后尝试进行修复。但是需要注意的是，我们所有的人员都是志愿者，有时候一个错误报告可能会很长时间没有人来进行回复。如果可以的话，添加新的信息将会有助于早点修复错误，但是请不要添加非描述性的评论来将“炒热”该错误。< / p >
< p > 切记， ， ， ， ， ， < / p >
2010-07-08 22:03:41 +04:00
< / div >
< / div >
< div class = "nav" >
< div class = "inner" > < span >
< a href = "../welcome_zh_CN.html" class = "uplink" > Welcome< / a >
< / span > < / div >
< / div >
< / body >
< / html >
