Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
F
ffmpeg
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
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
ffmpeg
Commits
2cd40680
Commit
2cd40680
authored
Jan 29, 2013
by
Anton Khirnov
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
fraps: fix off-by one bug for version 1.
CC:libav-stable@libav.org
parent
da7baaaa
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
3 additions
and
3 deletions
+3
-3
cmdutils.c
cmdutils.c
+1
-1
fraps.c
libavcodec/fraps.c
+1
-1
fraps-v1
tests/ref/fate/fraps-v1
+1
-1
No files found.
cmdutils.c
View file @
2cd40680
...
...
@@ -1566,7 +1566,7 @@ static int alloc_buffer(FrameBuffer **pool, AVCodecContext *s, FrameBuffer **pbu
/* XXX this shouldn't be needed, but some tests break without this line
* those decoders are buggy and need to be fixed.
* the following tests fail:
*
fraps-v1,
qtrle-1bit
* qtrle-1bit
*/
memset
(
buf
->
base
[
0
],
128
,
ret
);
...
...
libavcodec/fraps.c
View file @
2cd40680
...
...
@@ -239,7 +239,7 @@ static int decode_frame(AVCodecContext *avctx,
if
(
f
->
pict_type
==
AV_PICTURE_TYPE_I
)
{
for
(
y
=
0
;
y
<
avctx
->
height
;
y
++
)
memcpy
(
&
f
->
data
[
0
][(
avctx
->
height
-
y
)
*
f
->
linesize
[
0
]],
memcpy
(
&
f
->
data
[
0
][(
avctx
->
height
-
y
-
1
)
*
f
->
linesize
[
0
]],
&
buf
[
y
*
avctx
->
width
*
3
],
3
*
avctx
->
width
);
}
...
...
tests/ref/fate/fraps-v1
View file @
2cd40680
#tb 0: 1/25
0, 0, 0, 1, 230400, 0x
6bc891ff
0, 0, 0, 1, 230400, 0x
23c29d17
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