Bug #5874
closedCoverity output for Ruby 1.9.3
Description
Hi guys,
I'm not sure if you have access to Coverity [1], but I ran it on Ruby 1.9.3 and I just wanted to post the output here so you can go through it and maybe make some adjustments to make the code better.
Regards,
Bohuslav.
Files
Updated by mame (Yusuke Endoh) almost 13 years ago
- Status changed from Open to Rejected
- Assignee set to mame (Yusuke Endoh)
Hello,
Thank you for your reporting.
Fortunately, Coverity kindly provides us the daily analysis
results for Ruby [1]. IOW, some of Ruby developers have an
(indirect) access to Coverity Prevent.
[1] http://scan.coverity.com/rung2.html
I checked all the errors a few years ago. It was indeed
helpful us find some faults, though there were also many
false-positives (I don't mean to blame Prevent. They was
actually hard even for human to determine if each error is
false-positive or not)
Anyway, I attempted to vanish the errors. But I gave up.
This is becuase the update is once a day, which means I
could not check if my fix was actually effective or not
until the next day. It was too frustrating, at least, for
me.
I'm thus closing this ticket as wontfix.
If you give us the report as a sequence of patchs, we will
really appreciate it :-)
--
Yusuke Endoh mame@tsg.ne.jp