Live data from Hacker News

We found a division by zero bug in FFmpeg with a vibecoded fuzzer

code.ffmpeg.org

41–50 of 274 posts

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#41

Earlier quoted context omitted.

Those sneaky LLMs going 7 years into the past and committing as a human: https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/8eda3c7f91e1a5b...

It’s obviously Claude 69 with time travel functionality, that’s too dangerous to release to public. They’re working on space-time limiting sandbox to prevent these issues.

Just remember kids, never immanentize the eschaton.

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#42
post #4

Earlier quoted context omitted.

Finding the bugs with LLMs is easy. Reviewing the output, cleaning it up, and making sure it doesn't break something else is the hard part.

No one can keep up with the volume of code AI produces. We wont stop using AI. We will use AI to check AI. Of course this is crazy, but it will also unlock pretty insane scaling and productivity and ultimately we will manage it on either end via requirements and tests.

[deleted]

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#44
post #17

Earlier quoted context omitted.

I dislike AI, but if AI finds real bugs then this is in my opinion objectively a positive thing. Of course the question is what constitutes a real bug.

Unfiltered models will help build exploits for the bugs they find, so there is some means of measuring their efficacy.

If you're just talking about security bugs.

There are also non security bugs that don't have exploits but just make the user experience worse.

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#45

Earlier quoted context omitted.

I dislike AI, but if AI finds real bugs then this is in my opinion objectively a positive thing. Of course the question is what constitutes a real bug.

A.I. is useful for this. But it would be even more useful if all new code were written in Rust or some other memory-safe language. A.I. could also be used to port C/C++ codebases to Rust, which isn't economically feasible at the moment.

AI will have plenty of security bugs left to find in Rust codebases.

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#46
post #35

[flagged]

Unrelated to the submitted link -- just checked your comment history and all of your comments are AI-generated like this one. What's the motivation for this?

He won’t reply, he’s busy promoting himself and his peojects with AI.

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#48
post #35

[flagged]

Unrelated to the submitted link -- just checked your comment history and all of your comments are AI-generated like this one. What's the motivation for this?

probably karma farming

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#50

Earlier quoted context omitted.

No one can keep up with the volume of code AI produces. We wont stop using AI. We will use AI to check AI. Of course this is crazy, but it will also unlock pretty insane scaling and productivity and ultimately we will manage it on either end via requirements and tests.

It's mostly (not entirely, but mostly) finding security issues in old human-written code. It'll eventually start running out of those. From that standpoint, it's not a crazy setup security-wise. Maybe still crazy for development.

You can point AI at any AI produced code and ask it to review it, get back 10 bullet points and a few pages of prose. And the fun part is, you can do that over and over and over again!
Post reply on HN