Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
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
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
f289422a
Commit
f289422a
authored
Apr 07, 2015
by
Michael Niedermayer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
avformat/ape: Use av_malloc_array()
Signed-off-by:
Michael Niedermayer
<
michaelni@gmx.at
>
parent
3662e251
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
ape.c
libavformat/ape.c
+1
-1
No files found.
libavformat/ape.c
View file @
f289422a
...
@@ -268,7 +268,7 @@ static int ape_read_header(AVFormatContext * s)
...
@@ -268,7 +268,7 @@ static int ape_read_header(AVFormatContext * s)
ape
->
seektablelength
/
sizeof
(
*
ape
->
seektable
),
ape
->
totalframes
);
ape
->
seektablelength
/
sizeof
(
*
ape
->
seektable
),
ape
->
totalframes
);
return
AVERROR_INVALIDDATA
;
return
AVERROR_INVALIDDATA
;
}
}
ape
->
frames
=
av_malloc
(
ape
->
totalframes
*
sizeof
(
APEFrame
));
ape
->
frames
=
av_malloc
_array
(
ape
->
totalframes
,
sizeof
(
APEFrame
));
if
(
!
ape
->
frames
)
if
(
!
ape
->
frames
)
return
AVERROR
(
ENOMEM
);
return
AVERROR
(
ENOMEM
);
ape
->
firstframe
=
ape
->
junklength
+
ape
->
descriptorlength
+
ape
->
headerlength
+
ape
->
seektablelength
+
ape
->
wavheaderlength
;
ape
->
firstframe
=
ape
->
junklength
+
ape
->
descriptorlength
+
ape
->
headerlength
+
ape
->
seektablelength
+
ape
->
wavheaderlength
;
...
...
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