Many thanks for all replies. It provides the background info I was looking
for.
Thank you,
Mircea
On Thu, Feb 27, 2020 at 11:17 AM tth wrote:
> Le 27/02/2020 19:35:24, Nicolas George a écrit :
> > Carl Eugen Hoyos (12020-02-27):
> > > The abort() calls are not supposed to actually be hit. If
Le 27/02/2020 19:35:24, Nicolas George a écrit :
Carl Eugen Hoyos (12020-02-27):
> The abort() calls are not supposed to actually be hit. If you want
to
> catch them in your code using the libraries, you should do so.
But if the abort() are reached, that's a bug, either in FFmpeg or in
the
Carl Eugen Hoyos (12020-02-27):
> The abort() calls are not supposed to actually be hit. If you want to
> catch them in your code using the libraries, you should do so.
But if the abort() are reached, that's a bug, either in FFmpeg or in the
program that uses its libraries. Catching the signal is
> Am 27.02.2020 um 09:35 schrieb Mircea Carausu via ffmpeg-user
> :
>
> I noticed av_asser0 macro is extensively used in ffmpeg code... simple grep
> returns some 11xx hits.
> Inside this macro abort() call is used.
> Two questions in my mind:
> 1. why abort() and not exit() with a err code
> Am 27.02.2020 um 09:35 schrieb Mircea Carausu via ffmpeg-user
> :
>
> why abort() and not exit() with a err code (i.e. EXIT_FAILURE)
The proper answer here is that libraries are not supposed to call exit().
Carl Eugen
___
ffmpeg-user mailing list
Hello,
I noticed av_asser0 macro is extensively used in ffmpeg code... simple grep
returns some 11xx hits.
Inside this macro abort() call is used.
Two questions in my mind:
1. why abort() and not exit() with a err code (i.e. EXIT_FAILURE)
2, if we trigger abort purposely, why not have a signal