Hacker News new | ask | show | jobs
by H8crilA 993 days ago
Not sure why this is downvoted, the comment is on point. Is it because it is partly gpt-generated content?

I wonder if patching memory worked in the debugger, if not this would have to be done by manually editing the kernel file with IDA or something, and rebooting the machine. But in either case this is a good way to find the problem.

3 comments

That’s likely. ChatGPT is not reliable, dumping its explanation of an issue isn’t valuable. It’s noise.

Everything in the comment before that was great, no reason vote it down for that.

If you don't want to be seeing ChatGPT generated content here, you should downvote it to discourage the poster from doing so. This is a perfect use of a downvote IMHO.

If you don't mind or care enough, obviously don't downvote, and if you love it, upvote it. That's how we get our community to develop some shared standards of communication.

FWIW, if someone wants ChatGPT content, they can just go to ChatGPT too.

True, although in this case the ChatGPT explanation seems to be mostly accurate.

The one dubious point is the definition of "bisect". The definition is completely accurate in this context. But the sentence after the definition starts with "In this context,", implying that the definition itself should be relatively context-independent. Yet the term "bisect" in programming is more commonly used to refer to something slightly different: dividing some code's commit history into parts, not the code itself.

Also, several of the explanations are wordy and uninsightful, though not false.

…Admittedly, this is all beside the point. ChatGPT output carries a high risk of being inaccurate, so even if it's accurate in some specific case, readers have no way of knowing that. Which means that you shouldn't post ChatGPT output unless you can personally vouch for its accuracy, but in that case why use ChatGPT at all? Still, in this case I'll retrospectively vouch for it.

I added the ChatGPT explanation after the fact because I thought some readers might not have the background to understand the original explanation and I could vouch for its accuracy.

Honestly didn't expect it to cause such a backlash in this forum...

It must have been editing the file on disk. The debugger was what was causing the crash in the first place.