Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [WIP] False positives on Coverity
Date: Tue, 14 May 2024 09:37:20 +0200
Message-ID: <3a647bc5a15399b3217530566f05ee7d77b530db.camel@haerdin.se> (raw)
In-Reply-To: <20240513233816.GL6420@pb2>

Formal methods would be better than the heuristics coverity uses. At
the moment such methods are still too expensive for general use except
for the most safety critical applications (aerospace etc). But perhaps
in time the tooling and SMT solvers will improve sufficiently to make
it commonplace.

For FFmpeg the Eva and WP plugins for Frama-C would be of relevance.
I've been toying with the idea on and off

/Tomas
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2024-05-14  7:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 23:38 Michael Niedermayer
2024-05-14  7:37 ` Tomas Härdin [this message]
2024-05-14 11:28   ` Rémi Denis-Courmont
2024-05-15  8:06     ` Tomas Härdin
2024-06-08 16:01 ` Michael Niedermayer
2024-06-08 19:49   ` Vittorio Giovara
2024-06-08 22:49     ` Timo Rothenpieler
2024-06-09 13:10       ` Vittorio Giovara
2024-06-09 22:04         ` Michael Niedermayer
2024-06-10 12:37           ` Vittorio Giovara
2024-06-10 12:40             ` Timo Rothenpieler
2024-06-10 12:45               ` Vittorio Giovara
2024-06-11 15:46                 ` Michael Niedermayer
2024-06-09 22:02       ` Michael Niedermayer
2024-07-11 23:55 ` Michael Niedermayer
2024-07-12 23:20   ` Michael Niedermayer
2024-07-25 14:41     ` Michael Niedermayer
2024-08-12 17:40       ` Michael Niedermayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3a647bc5a15399b3217530566f05ee7d77b530db.camel@haerdin.se \
    --to=git@haerdin.se \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git