|
|
1.
|
|
|
% How to submit a Rust bug report
|
|
|
type: Plain text
|
|
|
|
|
% 如何提交Rust错误报告
|
|
Translated and reviewed by
Liigo
|
|
|
|
Located in
src/doc/complement-bugreport.md:2
|
|
|
2.
|
|
|
# I think I found some bugs in rustc compiler!
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
src/doc/complement-bugreport.md:4
|
|
|
3.
|
|
|
If you see this message: `error: internal compiler error: unexpected failure`, then you have definitely found a bug in the compiler. It's also possible that your code is not well-typed, but if you saw this message, it's still a bug in error reporting.
|
|
|
type: Plain text
|
|
|
|
|
如果你看到提示：“错误：内部编译器错误：意外失败”，很明显是发现 了编译器的Bug。即使因你写的代码问题而导致此错误，也应该认为这是编译器的错误。
|
|
Translated and reviewed by
Liigo
|
|
|
|
Located in
src/doc/complement-bugreport.md:9
|
|
|
4.
|
|
|
If you see a message about an LLVM assertion failure, then you have also definitely found a bug in the compiler. In both of these cases, it's not your fault and you should report a bug!
|
|
|
type: Plain text
|
|
|
|
|
如果看到提示说LLVM断言失败，也很可能发现了编译器的Bug。无论哪种情况，都不是您的问题，请提交Bug报告给我们。
|
|
Translated and reviewed by
Liigo
|
|
|
|
Located in
src/doc/complement-bugreport.md:13
|
|
|
5.
|
|
|
If you see a compiler error message that you think is meant for users to see, but it confuses you, *that's a bug too*. If it wasn't clear to you, then it's an error message we want to improve, so please report it so that we can try to make it better.
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
src/doc/complement-bugreport.md:18
|
|
|
6.
|
|
|
Liigo add this line. 1.
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
src/doc/complement-bugreport.md:20
|
|
|
7.
|
|
|
# How do I know the bug I found isn't a bug that already exists in the issue tracker?
|
|
|
type: Plain text
|
|
|
|
|
# 如何知道我发现的Bug已经在错误跟踪列表里面？
|
|
Translated and reviewed by
Liigo
|
|
|
|
Located in
src/doc/complement-bugreport.md:22
|
|
|
8.
|
|
|
If you don't have enough time for a search, then don't worry about that. Just submit the bug. If it's a duplicate, somebody will notice that and close it during triage.
|
|
|
type: Plain text
|
|
|
|
|
如果您没有时间去查询，没关系，只管提交Bug报告就行，如果重复了，会有人处理的。
|
|
Translated and reviewed by
Liigo
|
|
|
|
Located in
src/doc/complement-bugreport.md:25
|
|
|
9.
|
|
|
If you have the time for it, it would be useful to type the text of the error message you got [into the issue tracker search box](https://github.com/rust-lang/rust/issues) to see if there's an existing bug that resembles your problem. If there is, and it's an open bug, you can comment on that issue and say you are also affected. This will encourage the devs to fix it. But again, don't let this stop you from submitting a bug. We'd rather have to do the work of closing duplicates than miss out on valid bug reports.
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
src/doc/complement-bugreport.md:33
|
|
|
10.
|
|
|
Liigo add this line. 2.
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
src/doc/complement-bugreport.md:35
|
