|
|
17.
|
|
|
Screenshots can be very helpful sometimes. You can attach them to the bug report after it is posted to the bug tracking system.
|
| Context: |
|
@info/rich
|
|
|
|
|
屏幕截图可能非常有用。您可以稍后将其作为报告的附件提交到错误追踪系统。
|
|
Translated by
Feng Chao
|
|
Reviewed by
Feng Chao
|
|
|
|
Located in
aboutbugreportingdialog.cpp:85
|
|
|
18.
|
|
|
Crash Information (backtrace)
|
| Context: |
|
@title
|
|
|
|
|
崩溃信息(回溯跟踪)
|
|
Translated by
nihui
|
|
|
|
Located in
aboutbugreportingdialog.cpp:90
|
|
|
19.
|
|
|
This page will generate a "backtrace" of the crash. This is information that tells the developers where the application crashed.
|
| Context: |
|
@info/rich
|
|
|
|
|
此页面会生成一份有关崩溃的“回溯跟踪”信息，它会告诉开发者程序是在何处崩溃的。
|
|
Translated by
Lie Ex
|
|
|
|
Located in
aboutbugreportingdialog.cpp:92
|
|
|
20.
|
|
|
If the crash information is not detailed enough, you may need to install some debug packages and reload it (if the <interface>Install Debug Symbols</interface> button is available you can use it to automatically install the missing information.)
|
| Context: |
|
@info/rich
|
|
|
|
|
如果崩溃信息不够详细，您可能需要安装一些调试程序包并重新加载它(如果<interface>安装调试符号</interface>按钮可用，您可以直接通过它自动装入缺失的信息。)
|
|
Translated by
Lie Ex
|
|
|
|
Located in
aboutbugreportingdialog.cpp:95
|
|
|
21.
|
|
|
You can find more information about backtraces, what they mean, and how they are useful at <link>%1</link>
|
| Context: |
|
@info/rich
|
|
|
|
|
您可以找到更多有关回溯跟踪的信息，比如它的含义以及作用，参考链接 <link>%1</link>
|
|
Translated by
Lie Ex
|
|
|
|
Located in
aboutbugreportingdialog.cpp:99
|
|
|
22.
|
|
|
Once you get a useful backtrace (or if you do not want to install the missing debugging packages) you can continue.
|
| Context: |
|
@info/rich
|
|
|
|
|
如果您得到了有用的回溯跟踪(或是您不打算安装缺失的调试软件包)，可以继续。
|
|
Translated by
nihui
|
|
|
|
Located in
aboutbugreportingdialog.cpp:101
|
|
|
23.
|
|
|
Conclusions
|
| Context: |
|
@title
|
|
|
|
|
结论
|
|
Translated by
Feng Chao
|
|
Reviewed by
Feng Chao
|
|
|
|
Located in
aboutbugreportingdialog.cpp:106
|
|
|
24.
|
|
|
Using the quality of the crash information gathered, and your answers on the previous page, the assistant will tell you if the crash is worth reporting or not.
|
| Context: |
|
@info/rich
|
|
|
|
|
根据所收集崩溃信息的质量和您在前一页的回答，此助手会告诉您提交这份报告的必要性。
|
|
Translated by
Feng Chao
|
|
Reviewed by
Feng Chao
|
|
|
|
Located in
aboutbugreportingdialog.cpp:108
|
|
|
25.
|
|
|
If the crash is worth reporting but the application is not supported in the KDE bug tracking system, you will need to directly contact the maintainer of the application.
|
| Context: |
|
@info/rich
|
|
|
|
|
如果这个崩溃值得报告，但 KDE 错误追踪系统却不支持此程序，需要您直接联系程序的维护者。
|
|
Translated by
Feng Chao
|
|
Reviewed by
Feng Chao
|
|
|
|
Located in
aboutbugreportingdialog.cpp:111
|
|
|
26.
|
|
|
If the crash is listed as being not worth reporting, and you think the assistant has made a mistake, you can still manually report the bug by logging into the bug tracking system. You can also go back and change information and download debug packages.
|
| Context: |
|
@info/rich
|
|
|
|
|
如果本助手认为这份崩溃报告没有提交的必要，但是您认为它的判断有误，您仍然可以登录到我们的错误追踪系统进行手动报告，或是返回更改要提交的信息并下载缺失的调试软件包。
|
|
Translated by
Feng Chao
|
|
Reviewed by
Feng Chao
|
|
|
|
Located in
aboutbugreportingdialog.cpp:114
|
