Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
W
wine-winehq
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-winehq
Commits
4d30e7af
Commit
4d30e7af
authored
May 08, 2009
by
Alexandre Julliard
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
oleaut32/tests: Use the correct allocator in the ClearCustData test.
parent
18419dab
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
9 deletions
+1
-9
vartype.c
dlls/oleaut32/tests/vartype.c
+1
-9
No files found.
dlls/oleaut32/tests/vartype.c
View file @
4d30e7af
...
...
@@ -5788,21 +5788,13 @@ static void test_UintChangeTypeEx(void)
static
void
test_ClearCustData
(
void
)
{
WCHAR
buff
[
sizeof
(
CUSTDATAITEM
)
*
NUM_CUST_ITEMS
/
sizeof
(
WCHAR
)];
CUSTDATA
ci
;
unsigned
i
;
CHECKPTR
(
ClearCustData
);
memset
(
buff
,
0
,
sizeof
(
buff
));
ci
.
cCustData
=
NUM_CUST_ITEMS
;
/* This is a bit tricky. We use SysAllocStringByteLen to allocate the
* array, since native uses an internal IMalloc interface for allocating
* its memory, while Wine uses HeapAlloc(). Doing this ensures we allocate
* using the correct function whether with native or builtin.
*/
ci
.
prgCustData
=
(
LPCUSTDATAITEM
)
Get
(
SysAllocStringByteLen
((
LPCSTR
)
buff
,
sizeof
(
buff
)));
ci
.
prgCustData
=
CoTaskMemAlloc
(
sizeof
(
CUSTDATAITEM
)
*
NUM_CUST_ITEMS
);
for
(
i
=
0
;
i
<
NUM_CUST_ITEMS
;
i
++
)
VariantInit
(
&
ci
.
prgCustData
[
i
].
varValue
);
pClearCustData
(
&
ci
);
...
...
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