We found a division by zero bug in FFmpeg with a vibecoded fuzzer
1–10 of 274 posts
Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer
#2It’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.
Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer
#3It’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 don't care if you call it an over-engineered looping machine or what, there are concrete benefits to using LLMs for this. They work faster than developing your own looping algorithm and more often produce useful results than not.
Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer
#4It’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.
Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer
#5It’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.
But what's your expectation of the net?
Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer
#6The 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.
Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer
#7The 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.
Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer
#8It’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.
[deleted]
Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer
#9send patches
Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer
#10The 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.
Those sneaky LLMs going 7 years into the past and committing as a human:
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/8eda3c7f91e1a5b...