Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
int
Rust
提交
8a7b1bca
R
Rust
项目概览
int
/
Rust
大约 1 年 前同步成功
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
R
Rust
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
8a7b1bca
编写于
3月 25, 2016
作者:
N
Niko Matsakis
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update backtrace test for FIXME on windows
上级
24059f74
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
20 addition
and
3 deletion
+20
-3
src/test/run-pass/backtrace.rs
src/test/run-pass/backtrace.rs
+20
-3
未找到文件。
src/test/run-pass/backtrace.rs
浏览文件 @
8a7b1bca
...
@@ -51,13 +51,30 @@ fn template(me: &str) -> Command {
...
@@ -51,13 +51,30 @@ fn template(me: &str) -> Command {
return
m
;
return
m
;
}
}
fn
expected
(
fn_name
:
&
str
)
->
String
{
// FIXME(#32481)
//
// On windows, we read the function name from debuginfo using some
// system APIs. For whatever reason, these APIs seem to use the
// "name" field, which is only the "relative" name, not the full
// name with namespace info, so we just see `foo` and not
// `backtrace::foo` as we see on linux (which uses the linkage
// name).
if
cfg!
(
windows
)
{
format!
(
" - {}"
,
fn_name
)
}
else
{
format!
(
" - backtrace::{}"
,
fn_name
)
}
}
fn
runtest
(
me
:
&
str
)
{
fn
runtest
(
me
:
&
str
)
{
// Make sure that the stack trace is printed
// Make sure that the stack trace is printed
let
p
=
template
(
me
)
.arg
(
"fail"
)
.env
(
"RUST_BACKTRACE"
,
"1"
)
.spawn
()
.unwrap
();
let
p
=
template
(
me
)
.arg
(
"fail"
)
.env
(
"RUST_BACKTRACE"
,
"1"
)
.spawn
()
.unwrap
();
let
out
=
p
.wait_with_output
()
.unwrap
();
let
out
=
p
.wait_with_output
()
.unwrap
();
assert
!
(
!
out
.status
.success
());
assert
!
(
!
out
.status
.success
());
let
s
=
str
::
from_utf8
(
&
out
.stderr
)
.unwrap
();
let
s
=
str
::
from_utf8
(
&
out
.stderr
)
.unwrap
();
assert
!
(
s
.contains
(
"stack backtrace"
)
&&
s
.contains
(
" - backtrace::foo"
),
assert
!
(
s
.contains
(
"stack backtrace"
)
&&
s
.contains
(
&
expected
(
"foo"
)
),
"bad output: {}"
,
s
);
"bad output: {}"
,
s
);
// Make sure the stack trace is *not* printed
// Make sure the stack trace is *not* printed
...
@@ -67,7 +84,7 @@ fn runtest(me: &str) {
...
@@ -67,7 +84,7 @@ fn runtest(me: &str) {
let
out
=
p
.wait_with_output
()
.unwrap
();
let
out
=
p
.wait_with_output
()
.unwrap
();
assert
!
(
!
out
.status
.success
());
assert
!
(
!
out
.status
.success
());
let
s
=
str
::
from_utf8
(
&
out
.stderr
)
.unwrap
();
let
s
=
str
::
from_utf8
(
&
out
.stderr
)
.unwrap
();
assert
!
(
!
s
.contains
(
"stack backtrace"
)
&&
!
s
.contains
(
" - backtrace::foo"
),
assert
!
(
!
s
.contains
(
"stack backtrace"
)
&&
!
s
.contains
(
&
expected
(
"foo"
)
),
"bad output2: {}"
,
s
);
"bad output2: {}"
,
s
);
// Make sure a stack trace is printed
// Make sure a stack trace is printed
...
@@ -77,7 +94,7 @@ fn runtest(me: &str) {
...
@@ -77,7 +94,7 @@ fn runtest(me: &str) {
let
s
=
str
::
from_utf8
(
&
out
.stderr
)
.unwrap
();
let
s
=
str
::
from_utf8
(
&
out
.stderr
)
.unwrap
();
// loosened the following from double::h to double:: due to
// loosened the following from double::h to double:: due to
// spurious failures on mac, 32bit, optimized
// spurious failures on mac, 32bit, optimized
assert
!
(
s
.contains
(
"stack backtrace"
)
&&
s
.contains
(
" - backtrace::double"
),
assert
!
(
s
.contains
(
"stack backtrace"
)
&&
s
.contains
(
&
expected
(
"double"
)
),
"bad output3: {}"
,
s
);
"bad output3: {}"
,
s
);
// Make sure a stack trace isn't printed too many times
// Make sure a stack trace isn't printed too many times
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录