Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
linux
Commits
2f38795e
Commit
2f38795e
authored
Mar 03, 2003
by
David Mosberger
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
ia64: Correct region_start calculation in kernel unwinder.
parent
0b25bc5e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
5 deletions
+6
-5
arch/ia64/kernel/unwind.c
arch/ia64/kernel/unwind.c
+6
-5
No files found.
arch/ia64/kernel/unwind.c
View file @
2f38795e
...
...
@@ -736,7 +736,7 @@ static void
desc_prologue
(
int
body
,
unw_word
rlen
,
unsigned
char
mask
,
unsigned
char
grsave
,
struct
unw_state_record
*
sr
)
{
int
i
;
int
i
,
region_start
;
if
(
!
(
sr
->
in_body
||
sr
->
first_region
))
finish_prologue
(
sr
);
...
...
@@ -748,19 +748,20 @@ desc_prologue (int body, unw_word rlen, unsigned char mask, unsigned char grsave
return
;
}
region_start
=
sr
->
region_start
+
sr
->
region_len
;
for
(
i
=
0
;
i
<
sr
->
epilogue_count
;
++
i
)
pop
(
sr
);
sr
->
epilogue_count
=
0
;
sr
->
epilogue_start
=
UNW_WHEN_NEVER
;
if
(
!
body
)
push
(
sr
);
sr
->
region_start
+=
sr
->
region_len
;
sr
->
region_start
=
region_start
;
sr
->
region_len
=
rlen
;
sr
->
in_body
=
body
;
if
(
!
body
)
{
push
(
sr
);
for
(
i
=
0
;
i
<
4
;
++
i
)
{
if
(
mask
&
0x8
)
set_reg
(
sr
->
curr
.
reg
+
unw
.
save_order
[
i
],
UNW_WHERE_GR
,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment