Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
llvm-epi
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Roger Ferrer
llvm-epi
Commits
184c6591
Commit
184c6591
authored
12 years ago
by
Andrew Kaylor
Browse files
Options
Downloads
Patches
Plain Diff
Generalizing expected stop reason string checking in InferiorCrashing test case.
llvm-svn: 171554
parent
cd330348
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
lldb/test/functionalities/inferior-crashing/TestInferiorCrashing.py
+7
-2
7 additions, 2 deletions
...functionalities/inferior-crashing/TestInferiorCrashing.py
with
7 additions
and
2 deletions
lldb/test/functionalities/inferior-crashing/TestInferiorCrashing.py
+
7
−
2
View file @
184c6591
...
...
@@ -39,14 +39,19 @@ class CrashingInferiorTestCase(TestBase):
self
.
runCmd
(
"
run
"
,
RUN_SUCCEEDED
)
if
sys
.
platform
.
startswith
(
"
darwin
"
):
stop_reason
=
'
stop reason = EXC_BAD_ACCESS
'
else
:
stop_reason
=
'
stop reason = invalid address
'
# The stop reason of the thread should be a bad access exception.
self
.
expect
(
"
thread list
"
,
STOPPED_DUE_TO_EXC_BAD_ACCESS
,
substrs
=
[
'
stopped
'
,
'
stop
reason
= EXC_BAD_ACCESS
'
])
stop
_
reason
])
# And it should report the correct line number.
self
.
expect
(
"
thread backtrace all
"
,
substrs
=
[
'
stop
reason
= EXC_BAD_ACCESS
'
,
substrs
=
[
stop
_
reason
,
'
main.c:%d
'
%
self
.
line
])
def
inferior_crashing_python
(
self
):
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment