yxliang

@cgewecke - The json coverage format you wrote is fine. (p.s., it's an object not an array) - Now, I think that the array associated with one line in one...

@cgewecke Ok, now this object looks really better. But, as suggested, there might be tests with the same description. I can think of two ways to deal with this. For...

Same goes to `abi`. You can't compile without outputting `abi`... Problematic code: https://github.com/ethereum/py-solc/blob/fc76877f5b9bb577b2cd66abcb6d1df443156d0d/solc/main.py#L72

Same here! When I update the `mockgoose`, things will break... I haven't succeeded fixing it yet...

I have tried `-std=c89` and it works. However, the target program that I want to run with KLEE contains C99 features. Would be great if there is some quick workaround...

@MartinNowack Program used: ```c #include int main(int argc, char** argv) { int a; scanf("%d", &a); printf("%d", a); return 0; } ``` Compiled using wllvm with `clang` version 3.4 and flag...

Thanks @MartinNowack. However, like what I said in the previous comment, the target programs that I want to run with KLEE requires `C99`. Therefore, using `-std=c89` is not a solution...

@MartinNowack Thanks for the workaround. However... It didn't work for me. Could you share your experiment setting and did you modify base on commit 495b3e5 ? Thanks

@MartinNowack Indeed, this workaround works if the base is the pr #868 . Do you know which part of #868 is crucial for `replaceOrRenameFunction` function to be functional? Since I...

@MartinNowack Are there other quick fixes or workarounds that don't use `replaceOrRenameFunction`? So that, the bug related to `replaceOrRenameFunction` is not needed to be fixed by manually porting klee/klee#868. The...