Bug 80675
Summary: | bad source code | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | d.binderman |
Component: | kakasi | Assignee: | Akira TAGOH <tagoh> |
Status: | CLOSED RAWHIDE | QA Contact: | Bill Huang <bhuang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-04-25 07:11:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
d.binderman
2002-12-29 17:41:43 UTC
I not sure whether it's happened at this point, but right now I don't think kakasi still has a problem. although 'buffer' is actually allocated for k2rom_buflen(10) spaces, and basically it allows to use 9 spaces for something and 1 space for null string. So: buffer[k2rom_buflen] = '\0'; clen = k2rom_buflen; for (i = 0; i < k2rom_buflen; ++ i) { these codes are fine. I can't see any codes to be having the problems. I think that's a compiler bug or excessive warning. I can't believe your answer. It is standard C that if an array of size 'n' is declared, then the array index 'n' should not be used. Lower limits are inclusive, upper limits are exclusive. I strongly recommend reading page 22, section 1.6, of Kernighan & Ritchie Edition 2, the standard book on the C programming language. You are right. I was confused. fixed in 2.3.4-11 |