CC: ffmpeg/libavdevice/vtun_enc.c ffmpeg/libavdevice/vtun_enc.c: In function ‘vtun_write_uncoded_frame’:
ffmpeg/libavdevice/vtun_enc.c:318:60: warning: format ‘%lld’ expects argument of type ‘long long int’, but argument 4 has type ‘int64_t’ {aka ‘long int’} [-Wformat=]
318 | av_log(priv, AV_LOG_DEBUG, "vtun drop frame pts:%lld selected=%d\n", dequeue_frame->pts, selected);
| ~~~^ ~~~~~~~~~~~~~~~~~~
| | |
| long long int int64_t {aka long int}
| %ld
Signed-off-by: p-chenhaijun10 <p-chenhaijun10@xiaomi.com>
ffmpeg/libavdevice/nuttx.c:206:5: error: implicit declaration of function 'close'; did you mean 'pclose'? [-Werror=implicit-function-declaration]
206 | close(fd);
| ^~~~~
| pclose
At top level:
ffmpeg/libavfilter/af_amix.c:727:5: error: implicit declaration of function 'close'; did you mean 'pclose'? [-Werror=implicit-function-declaration]
727 | close(s->timer_fd);
| ^~~~~
| pclose
ffmpeg/libavfilter/af_amix.c: In function 'process_command':
ffmpeg/libavfilter/af_amix.c:806:13: error: implicit declaration of function 'read'; did you mean 'fread'? [-Werror=implicit-function-declaration]
806 | read(pollfd->fd, &exp, sizeof(exp));
| ^~~~
| fread
ffmpeg/libavfilter/sink_movie_async.c:82:5: error: unknown type name 'pthread_cond_t'
82 | pthread_cond_t cond;
| ^~~~~~~~~~~~~~
ffmpeg/libavfilter/sink_movie_async.c: In function 'moviesink_send_cmd':
ffmpeg/libavfilter/sink_movie_async.c:116:5: error: implicit declaration of function 'pthread_mutex_lock' [-Werror=implicit-function-declaration]
116 | pthread_mutex_lock(&priv->mutex);
| ^~~~~~~~~~~~~~~~~~
ffmpeg/libavfilter/sink_movie_async.c:118:5: error: implicit declaration of function 'pthread_cond_signal' [-Werror=implicit-function-declaration]
118 | pthread_cond_signal(&priv->cond);
| ^~~~~~~~~~~~~~~~~~~
ffmpeg/libavfilter/sink_movie_async.c:119:5: error: implicit declaration of function 'pthread_mutex_unlock'; did you mean 'nxrmutex_unlock'? [-Werror=implicit-function-declaration]
119 | pthread_mutex_unlock(&priv->mutex);
| ^~~~~~~~~~~~~~~~~~~~
| nxrmutex_unlock
ffmpeg/libavfilter/sink_movie_async.c: In function 'moviesink_thread':
ffmpeg/libavfilter/sink_movie_async.c:669:13: error: implicit declaration of function 'pthread_cond_wait' [-Werror=implicit-function-declaration]
669 | pthread_cond_wait(&priv->cond, &priv->mutex);
| ^~~~~~~~~~~~~~~~~
ffmpeg/libavfilter/sink_movie_async.c: In function 'moviesink_uninit':
ffmpeg/libavfilter/sink_movie_async.c:763:5: error: implicit declaration of function 'pthread_mutex_destroy'; did you mean 'nxrmutex_destroy'? [-Werror=implicit-function-declaration]
763 | pthread_mutex_destroy(&priv->mutex);
| ^~~~~~~~~~~~~~~~~~~~~
| nxrmutex_destroy
ffmpeg/libavfilter/sink_movie_async.c:764:5: error: implicit declaration of function 'pthread_cond_destroy' [-Werror=implicit-function-declaration]
Signed-off-by: anjiahao <anjiahao@xiaomi.com>
When recording PCM data with the parameters format=s16le:sample_rate=48000:ch_layout=mono, the size is 45. The memcpy buffer size on the driver side is 32, which is too small, leading to an overflow and overwriting values on the stack.
Signed-off-by: zhangsenlin <zhangsenlin@xiaomi.com>
While we only add the flag if the linker seems to support it,
it turns out that ld.bfd had a bug where the flag is accidentally
accepted, and the flag produces an output file named
"_warn_duplicate_libraries".
The ld.bfd bug was fixed in binutils 2.36, in
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=3991c7acb29aa8d7d52150695eb3efa03a08dd50.
Signed-off-by: Martin Storsjö <martin@martin.st>
"int-list" options are a hack that provides rudimentary support for
array-type options by treating them as byte arrays (i.e.
AV_OPT_TYPE_BINARY). Since we now have proper array-type options, they
should replace "int-list" everywhere (which happens to be just
buffersink).
I plan to look after and test them for the forseeable future.
I am not a committer but do care for these muxers/demuxers.
Signed-off-by: Marth64 <marth64@proxyid.net>
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
In the early return when both draw_bars and signal_loss_action
options are used, the context allocated previously was not
properly freed.
Introduced in 9bcb86b0fa58f1a5a2a8613065349e26abadb329
Fixes CID1619296
Signed-off-by: Marton Balint <cus@passwd.hu>
The block_buffer was only ever written to but then never used in the
following code, making it unnecessary.
Fixes a "variable 'block_buffer' set but not used" compiler warning.
jianglianfang