Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
W
wine-cw
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
wine
wine-cw
Commits
ce30db50
Commit
ce30db50
authored
Apr 01, 2020
by
Alexandre Julliard
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
kernel32: Avoid using memrchrW().
Signed-off-by:
Alexandre Julliard
<
julliard@winehq.org
>
parent
68587234
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
profile.c
dlls/kernel32/profile.c
+3
-3
No files found.
dlls/kernel32/profile.c
View file @
ce30db50
...
...
@@ -418,8 +418,8 @@ static PROFILESECTION *PROFILE_Load(HANDLE hFile, ENCODING * pEncoding)
if
(
*
szLineStart
==
'['
)
/* section start */
{
const
WCHAR
*
szSectionEnd
;
if
(
!
(
szSectionEnd
=
memrchrW
(
szLineStart
,
']'
,
szLineEnd
-
szLineStart
))
)
for
(
len
=
szLineEnd
-
szLineStart
;
len
>
0
;
len
--
)
if
(
szLineStart
[
len
-
1
]
==
']'
)
break
;
if
(
!
len
)
{
WARN
(
"Invalid section header at line %d: %s
\n
"
,
line
,
debugstr_wn
(
szLineStart
,
(
int
)(
szLineEnd
-
szLineStart
))
);
...
...
@@ -427,7 +427,7 @@ static PROFILESECTION *PROFILE_Load(HANDLE hFile, ENCODING * pEncoding)
else
{
szLineStart
++
;
len
=
(
int
)(
szSectionEnd
-
szLineStart
)
;
len
-=
2
;
/* no need to allocate +1 for NULL terminating character as
* already included in structure */
if
(
!
(
section
=
HeapAlloc
(
GetProcessHeap
(),
0
,
sizeof
(
*
section
)
+
len
*
sizeof
(
WCHAR
)
)))
...
...
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