Merge pull request #48 from Hyuntae-91/master

Translated and Updated document to Version 0.5.1

bugs.json

@@ -1,4 +1,38 @@
 [
+    {
+        "name": "ExpExponentCleanup",
+        "summary": "Using the ** operator with an exponent of type shorter than 256 bits can result in unexpected values.",
+        "description": "Higher order bits in the exponent are not properly cleaned before the EXP opcode is applied if the type of the exponent expression is smaller than 256 bits and not smaller than the type of the base. In that case, the result might be larger than expected if the exponent is assumed to lie within the value range of the type. Literal numbers as exponents are unaffected as are exponents or bases of type uint256.",
+        "fixed": "0.4.25",
+        "severity": "medium/high",
+        "check": {"regex-source": "[^/]\\*\\* *[^/0-9 ]"}
+    },
+    {
+        "name": "EventStructWrongData",
+        "summary": "Using structs in events logged wrong data.",
+        "description": "If a struct is used in an event, the address of the struct is logged instead of the actual data.",
+        "introduced": "0.4.17",
+        "fixed": "0.4.25",
+        "severity": "very low",
+        "check": {"ast-compact-json-path": "$..[?(@.nodeType === 'EventDefinition')]..[?(@.nodeType === 'UserDefinedTypeName' && @.typeDescriptions.typeString.startsWith('struct'))]"}
+    },
+    {
+        "name": "NestedArrayFunctionCallDecoder",
+        "summary": "Calling functions that return multi-dimensional fixed-size arrays can result in memory corruption.",
+        "description": "If Solidity code calls a function that returns a multi-dimensional fixed-size array, array elements are incorrectly interpreted as memory pointers and thus can cause memory corruption if the return values are accessed. Calling functions with multi-dimensional fixed-size arrays is unaffected as is returning fixed-size arrays from function calls. The regular expression only checks if such functions are present, not if they are called, which is required for the contract to be affected.",
+        "introduced": "0.1.4",
+        "fixed": "0.4.22",
+        "severity": "medium",
+        "check": {"regex-source": "returns[^;{]*\\[\\s*[^\\] \\t\\r\\n\\v\\f][^\\]]*\\]\\s*\\[\\s*[^\\] \\t\\r\\n\\v\\f][^\\]]*\\][^{;]*[;{]"}
+    },
+    {
+        "name": "OneOfTwoConstructorsSkipped",
+        "summary": "If a contract has both a new-style constructor (using the constructor keyword) and an old-style constructor (a function with the same name as the contract) at the same time, one of them will be ignored.",
+        "description": "If a contract has both a new-style constructor (using the constructor keyword) and an old-style constructor (a function with the same name as the contract) at the same time, one of them will be ignored. There will be a compiler warning about the old-style constructor, so contracts only using new-style constructors are fine.",
+        "introduced": "0.4.22",
+        "fixed": "0.4.23",
+        "severity": "very low"
+    },
     {
         "name": "ZeroFunctionSelector",
         "summary": "It is possible to craft the name of a function such that it is executed instead of the fallback function in very specific circumstances.",

bugs.rst

@@ -57,6 +57,17 @@
     버그를 유발하는 조건. 현재 이 객체는 부울값 ``optimizer`` 를 포함
     할 수 있습니다. 즉, 버그를 활성화하려면 optimizer를 켜야 합니다.
     조건이 주어지지 않으면, 버그가 있다고 간주됩니다.
+검사
+    이 필드에는 스마트 컨트랙트가 버그를 가지고 있는지 없는지를 
+    보고하는 여러가지 검사가 있습니다. 첫 번째 검사 유형은 Javascript 
+    정규식입니다. 이는 버그가 있는 경우 소스 코드("source-regex")와 
+    일치해야합니다. 일치하는 항목이 없다면, 버그가 존재하지 않을 가능성이 
+    높습니다. 반대로, 일치하는 항목이 있다면, 버그가 존재할 수 있습니다. 
+    정확성을 높이기 위해서 stripping 주석을 지운 뒤, 소스 코드에 검사를 
+    적용해야 합니다. 두번째 검사 유형은 Solidity 프로그램의 소형 
+    AST("ast-compact-json-path")에서 검사 할 패턴입니다.  특별한 검색 
+    쿼리는 JsonPath 표현식입니다. Solidity AST의 경로가 쿼리와 하나라도 
+    일치하지 않는 경우, 버그가 존재 할 수 있습니다.
 
 .. literalinclude:: bugs.json
    :language: js