5 ms·

No, the point here is that the fuzzer "caught" a bug in sqlite. The blog post mostly clears things up. To me it seemed pretty neutral just explaining it was act

No, the point here is that the fuzzer "caught" a bug in sqlite. The blog post mostly clears things up. To me it seemed pretty neutral just explaining it was actually with clang. No snarkyness our anything.

tom_mellior 6y ago
> No, the point here is that the fuzzer "caught" a bug in sqlite. The blog post mostly clears things up. Could you explain what you mean? What bug is there in sqlite? What blog post are you referring to? Via someone else in the thread, this was reported as a bug in LLVM, which was confirmed and is now fixed: https://bugs.llvm.org/show_bug.cgi?id=46194 https://bugs.llvm.org/show_bug.cgi?id=46194. In light of this, I wonder why you claim that this was a bug in sqlite.
- iforgotpassword 6y ago
  There is no bug in sqlite. That's the reason this blog post was written. And that's why it was interesting. Not because anyone claimed clang has a major fuckup.
  - loeg 6y ago
    You wrote earlier: > No, the point here is that the fuzzer "caught" a bug in sqlite. Which is where the confusion stems from. Perhaps "'caught a bug' in sqlite" would have been a more clear way of writing what you intended?
    - iforgotpassword 6y ago
      Ah I see now. Yes I could have extended the quotation. I was assuming the context was given by the start of the second paragraph: > OSSFuzz has been reported bug 23003 against SQLite.
- SQLite 6y ago
  What happened: 1. OSSFuzz reports a bug against SQLite. 2. SQLite dev tries to fix the reported problem but is unable to repro the bug on his desktop 3. SQLite dev replicates the OSSFuzz build environment which uses clang-11.0.0 and is then able to repro the reported bug 4. SQLite dev finds that the bug isn't in SQLite at all, but rather in clang-11.0.0 5. SQLite dev patches SQLite to work around the clang bug, posts a brief note about this on the SQLite forum, and goes to bed. 6. The post on the SQLite forum is picked up by HN while the SQLite dev is asleep. LLVM devs read HN, isolate and fix the clang problem, all before the SQLite dev wakes up.
  - andrewflnr 6y ago
    That's actually pretty awesome overall, besides the initial mis-attribution of the bug, which is an understandable mistake. Props to everyone involved.
  - jonas21 6y ago
    7. SQLite dev wakes up and responds to comments on HN!!
  - cheez 6y ago
    Hi, I love SQLite. It is the crux of a system that allows me to make a living.
  - throwaway_pdp09 6y ago
    SQLite dev tries... / SQLite dev replicates... / SQLite dev finds... / SQLite dev patches... Now compare this with what happens when you meet an MSSQL bug.
    - FridgeSeal 6y ago
      For those of us saddled with only the misfortune of having to use MSSQL and not having run into a bug yet, what's the experience?
      - throwaway_pdp09 6y ago

tom_mellior 6y ago

> No, the point here is that the fuzzer "caught" a bug in sqlite. The blog post mostly clears things up. Could you explain what you mean? What bug is there in sqlite? What blog post are you referring to? Via someone else in the thread, this was reported as a bug in LLVM, which was confirmed and is now fixed: https://bugs.llvm.org/show_bug.cgi?id=46194 https://bugs.llvm.org/show_bug.cgi?id=46194. In light of this, I wonder why you claim that this was a bug in sqlite.

iforgotpassword 6y ago
There is no bug in sqlite. That's the reason this blog post was written. And that's why it was interesting. Not because anyone claimed clang has a major fuckup.
- loeg 6y ago
  You wrote earlier: > No, the point here is that the fuzzer "caught" a bug in sqlite. Which is where the confusion stems from. Perhaps "'caught a bug' in sqlite" would have been a more clear way of writing what you intended?
  - iforgotpassword 6y ago
    Ah I see now. Yes I could have extended the quotation. I was assuming the context was given by the start of the second paragraph: > OSSFuzz has been reported bug 23003 against SQLite.
SQLite 6y ago
What happened: 1. OSSFuzz reports a bug against SQLite. 2. SQLite dev tries to fix the reported problem but is unable to repro the bug on his desktop 3. SQLite dev replicates the OSSFuzz build environment which uses clang-11.0.0 and is then able to repro the reported bug 4. SQLite dev finds that the bug isn't in SQLite at all, but rather in clang-11.0.0 5. SQLite dev patches SQLite to work around the clang bug, posts a brief note about this on the SQLite forum, and goes to bed. 6. The post on the SQLite forum is picked up by HN while the SQLite dev is asleep. LLVM devs read HN, isolate and fix the clang problem, all before the SQLite dev wakes up.
- andrewflnr 6y ago
  That's actually pretty awesome overall, besides the initial mis-attribution of the bug, which is an understandable mistake. Props to everyone involved.
- jonas21 6y ago
  7. SQLite dev wakes up and responds to comments on HN!!
- cheez 6y ago
  Hi, I love SQLite. It is the crux of a system that allows me to make a living.
- throwaway_pdp09 6y ago
  SQLite dev tries... / SQLite dev replicates... / SQLite dev finds... / SQLite dev patches... Now compare this with what happens when you meet an MSSQL bug.
  - FridgeSeal 6y ago
    For those of us saddled with only the misfortune of having to use MSSQL and not having run into a bug yet, what's the experience?
    - throwaway_pdp09 6y ago