Live data from Hacker News

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

code.ffmpeg.org

11–20 of 274 posts

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

#12
post #7

The fruits of using LLMs to code. You'll waste far more time finding what it quietly and subtly wrecked than you would have if you just coded it yourself.

You're not reading it right. The bug was found using a vibecoded fuzzer.

I wonder from where Claude stole this fuzzer.

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

#13
post #4
post #2

It’s interesting how AI may both raise and lower the quality of software. It’s very easy to send an AI agent on an open-ended bug hunt, and if it wastes a bunch of time and effort and finds nothing, no big deal. Time is much more important for a human developer with a salary.

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.

[flagged]

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

#14
post #2

It’s interesting how AI may both raise and lower the quality of software. It’s very easy to send an AI agent on an open-ended bug hunt, and if it wastes a bunch of time and effort and finds nothing, no big deal. Time is much more important for a human developer with a salary.

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.

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

#15
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.

[flagged]

> LLMs do find bugs, do save time

They find bugs but whether they save time is nowhere near as clear as you try to insinuate here.

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

#16

Earlier quoted context omitted.

[flagged]

> LLMs do find bugs, do save time They find bugs but whether they save time is nowhere near as clear as you try to insinuate here.

They save time in finding bugs.

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

#17
post #2

It’s interesting how AI may both raise and lower the quality of software. It’s very easy to send an AI agent on an open-ended bug hunt, and if it wastes a bunch of time and effort and finds nothing, no big deal. Time is much more important for a human developer with a salary.

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.

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

#18
post #16

Earlier quoted context omitted.

> LLMs do find bugs, do save time They find bugs but whether they save time is nowhere near as clear as you try to insinuate here.

They save time in finding bugs.

And for me they also save time in fixing bugs.

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

#20
post #2

It’s interesting how AI may both raise and lower the quality of software. It’s very easy to send an AI agent on an open-ended bug hunt, and if it wastes a bunch of time and effort and finds nothing, no big deal. Time is much more important for a human developer with a salary.

> It’s very easy to send an AI agent on an open-ended bug hunt, and if it wastes a bunch of time and effort and finds nothing, no big deal.

No big deal? It’s not like it’s free… tokens cost money.

Post reply on HN