[FFmpeg-user] abort and missing SIGABRT handling

[Mircea Carausu]

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 <sigfood at dinorama.fr> 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 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 likely to make
> > things worse. Remember that these asserts may be the final barrier
> > against an exploitable bug.
>
>     And in case of a catastophic event, with abort() you can
>     have a coredump for postmortem analysing...
>
>
> --
> -------( https://framasphere.org/tags/tetalab )-------------------------
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".