- 02 6月, 2018 40 次提交
-
-
由 charlesju1 提交于
Fixed history-plugin with option --filter-on receiver:action: does not add action trace for actor account
-
由 Greg Lee 提交于
-
由 Kevin Heifner 提交于
Build: fixed option behavior
-
由 Bill Hamilton 提交于
Merging master into eosio_build_symbol
-
由 Kevin Heifner 提交于
history_plugin: fixing potential integer overflow #3735
-
由 Bill Hamilton 提交于
-
由 arhag 提交于
Verify definition exists to prevent SEGFAULT
-
由 Kevin Heifner 提交于
-
由 arhag 提交于
Change to version 1.0.0, also update minimum gcc and clang versions.
-
由 arhag 提交于
-
由 arhag 提交于
Relocate wiki images and remove unused Doxyfile.
-
由 Anton Perkov 提交于
-
由 arhag 提交于
-
由 Jonathan Giszczak 提交于
-
由 Greg Lee 提交于
Bios boot tutorial: 200,000 accounts
-
由 Eric Iles 提交于
-
由 arhag 提交于
Remove sync test. Functionality covered by other tests.
-
由 arhag 提交于
Fix issue #3740
-
由 arhag 提交于
-
由 Todd Fleming 提交于
-
由 arhag 提交于
-
由 Jonathan Giszczak 提交于
-
由 arhag 提交于
-
由 Paul Calabrese 提交于
-
由 zorba80 提交于
-
由 Khaled Al-Hassanieh 提交于
-
由 Matt Witherspoon 提交于
zero wasm linear memory on memory growth
-
由 Todd Fleming 提交于
-
由 Jonathan Giszczak 提交于
-
由 arhag 提交于
Changed to better error message for buyram
-
由 arhag 提交于
-
由 Bucky Kittinger 提交于
-
由 arhag 提交于
-
由 Bucky Kittinger 提交于
-
由 arhag 提交于
-
由 arhag 提交于
add custom error messages to secondary index get
-
由 arhag 提交于
fix multiple bugs that were only exercised with malicious blocks
-
由 Kevin Heifner 提交于
fix llvm dependency from xenial to bionic on ubuntu:18.04
-
由 Matt Witherspoon 提交于
When a WASM grows its linear memory (via the grow_memory opcode) the new freshly accessible memory is required to be zeroed out. Our binaryen implementation needs a fix for this. WAVM is more interesting. It relies on a madvise(MADV_DONTNEED) to mark pages such that a subsequent access to those pages would be zero. This works on Linux.. but does not on macOS. It doesn't appear like this zero behavior that Linux performs is anything to do with what POSIX allows so macOS is probably within its rights to not zero memory. Change the WAVM memory growth to simply memset() on growth. This is a little undesirable because it means the memory will get zeroed twice on Linux (once in the memset and once in the kernel due to the madvise)
-
由 Todd Fleming 提交于
-