Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

code.ffmpeg.org

Post reply on HN
Print view View original

121–130 of 274 posts

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

#121

Post by bulder »

demibabs wrote: post #109
semiquaver wrote: post #108

Earlier quoted context omitted.

Oddly enough I can’t access that site, it just heats up my phone solving hashes. Gave up after about a minute and anubis had only made it less than halfway through. I doubt the real bots have any trouble bypassing it.

Yeah, is it trying to mine bitcoin or something? Anubis usually takes a second but here I waited a minute and got 20% through on a modern phone.

Presumably they've configured it to use a higher difficulty challenge due to high rates of scraping on their bugtracker

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

#122

Post by StilesCrisis »

black_knight wrote: post #71
astrange wrote: post #67

Earlier quoted context omitted.

Haskell's type system would not easily prevent this bug. It's not good at numeric/logic issues like that. When people say "Haskell makes it impossible to write bugs" they mean "Haskell has enums" (ADTs).

I am not claiming you cant write buggy code in Haskell! But following good functional style, your bug will more likely be compartmentalised, and fixing it will not break some other part of your program.

You can write good functional code in many languages. (Even C++!)

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

#123

Post by hiccuphippo »

semiquaver wrote: post #108
aeyes wrote: post #91

A patch for this was submitted in April: https://lists.ffmpeg.org/archives/list/ffmpeg-devel@ffmpeg.o... Edit: And there was discussion about this back in 2024 as well

Oddly enough I can’t access that site, it just heats up my phone solving hashes. Gave up after about a minute and anubis had only made it less than halfway through. I doubt the real bots have any trouble bypassing it.

Took less than a minute in my 5 year old xiaomi phone. It did take way longer than other Anubis sites I've seen.

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

#124

Post by black_knight »

StilesCrisis wrote: post #122
black_knight wrote: post #71

Earlier quoted context omitted.

I am not claiming you cant write buggy code in Haskell! But following good functional style, your bug will more likely be compartmentalised, and fixing it will not break some other part of your program.

You can write good functional code in many languages. (Even C++!)

Sure! I have done my fair share of pretending Java and C++ support my functional style. But at the end of the day, you have better support for writing that style in a real functional programming language. And I wonder how well one can enforce a functional style in say Java or C++ upon the LLMs. Who knows, they might be great at it?

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

#125

Post by bonoboTP »

adamddev1 wrote: post #79
nonethewiser wrote: post #34

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 will also unlock pretty insane scaling and productivity Insane scaling of bloat, bugs, and technical debt I'd say. > We will manage it on either end via requirements and tests It is so crazy that this is being touted as a sane strategy. When I was a much worse programmer, I tried to write a big complicated string manipulation function to take two types of scripts in a language and add diacritics. I had the requi…

You shared a story of a novice incompetent human programmer and this should tell us that AI is bad at coding.

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

#126

Post by Gigachad »

Spivak wrote: post #54
hn_submit wrote: post #38

Earlier quoted context omitted.

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.

I mean I get the sentiment but Rust won't save you against division by zero, it'll just panic at runtime like every other language.

From a security perspective, panic at runtime is not that bad for security. Much better than continuing to run with undefined behavior. If someone sends a malformed video in and it crashes the ffmpeg process you can just log it and restart it. Vs potentially exploiting the system.

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

#127

Post by Georgelemental »

bartread wrote: post #113
semiquaver wrote: post #108

Earlier quoted context omitted.

Oddly enough I can’t access that site, it just heats up my phone solving hashes. Gave up after about a minute and anubis had only made it less than halfway through. I doubt the real bots have any trouble bypassing it.

[flagged]

> And don't come crying to me about how the problem you're trying to solve is "hard". I don't care: you chose it, you chose to considerably worsen the web browsing experience of millions of people globally, nobody made you.

Unfortunately, if you let all the bots in, they overwhelm your servers, and then nobody can access the website.

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

#128

Post by aystatic »

Georgelemental wrote: post #127
bartread wrote: post #113

Earlier quoted context omitted.

[flagged]

> And don't come crying to me about how the problem you're trying to solve is "hard". I don't care: you chose it, you chose to considerably worsen the web browsing experience of millions of people globally, nobody made you. Unfortunately, if you let all the bots in, they overwhelm your servers, and then nobody can access the website.

Not if you use a decentralized peer-to-peer Git forge like https://radicle.network. If one node goes down, users can still access the same issues/PRs from another endpoint.

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

#129

Post by nextaccountic »

adamddev1 wrote: post #79
nonethewiser wrote: post #34

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 will also unlock pretty insane scaling and productivity Insane scaling of bloat, bugs, and technical debt I'd say. > We will manage it on either end via requirements and tests It is so crazy that this is being touted as a sane strategy. When I was a much worse programmer, I tried to write a big complicated string manipulation function to take two types of scripts in a language and add diacritics. I had the requi…

I'm not so sure LLM code today is below average. There was a time that things posted to dailywtf were normal everyday stuff
Post reply on HN