Connect community members with nonprofit board and volunteer opportunities.
zsusag/Grinnell-Linux-Printer-Installation 1
This repository contains the materials needed to get printers on the Grinnell College network working on a GNU/Linux system.
GrinnellAppDev/Lyles-Android 0
An Android application for Lyle's Pub
Trainee Project for Grinnell College's AppDev
Generic Makefile to build Arduino .ino sketches from the command line
An encrypted backup solution for GNU/Linux systems
This is a compiler created for CSC-312 at Grinnell College during the Spring 2018 semester.
push eventlahiri-phdworks/klee
push time in 7 days
push eventlahiri-phdworks/klee
commit sha e50f0ad0142c8ec87a9237480acc8f683fe0304a
Merge with old SpecialFunctionHandler.cpp/.h files
push time in 7 days
push eventlahiri-phdworks/klee
commit sha 458a57842a57cc739b6a46e716e2b90c3d70dd2f
Merge pull request #17 from klee/master Update from KLEE:Master
commit sha 63b7b3335f6ae1f3fa53dd6aeb3c7cd9aaefe934
Merge pull request #19 from klee/master Update from KLEE Master
commit sha dbe3e458d3e25fb092a5468a8fe551a6e7486aed
renaming 'libcxx' -> 'libc++'
commit sha 5f08b024bef12c3312d1e75f2c2ec5e5f5e0361f
add ifdefs for C++ exception handling restoring old behavior without EH support
commit sha b2157ca524c7c6ab8074f05b4c735a4fc237eb7d
add klee_messages for C++ exception handling support otherwise, it is hard to tell whether EH support is available or not
commit sha 5f8d562181bce7c0d11eae0a597e3f534966e42c
Executor: remove obsolete special case for __cxa_{re,}throw __cxa_throw and __cxa_rethrow were not handled by special function handlers in the final version of #966 (which introduced support for C++ exception handling)
commit sha 148a68df793fca84a36fefd8824ea54fdf6583f4
runtime/POSIX: fix failures with glibc-2.33 commit 8ed005daf0ab of glibc-2.33 (Remove stat wrapper functions, move them to exported symbols) removed renames of `__fxstat`, `__xstat`, and `__lxstat` to `__fxstat64`, `__xstat64`, and `__lxstat64`, respectively. But we relied on the renames to build `fd_64.c` properly. With glibc 2.33, we now see link failures of the POSIX runtime: error: Linking globals named '__xstat': symbol multiply defined! Rename the functions using `__REDIRECT_NTH` in the code as `__USE_FILE_OFFSET64` case (which we define at the top of the file by `#define _FILE_OFFSET_BITS 64`) did exactly that. Fixes #1384.
commit sha 295353010d23c9561826f811a59b7d5556c45596
Improved PR template by making it more succinct.
commit sha 91420b32cd347b43f64d337e5bd1f0855d0b247c
cmake: Fix warning about implicit type conversion Fixes: CMake Warning (dev) at CMakeLists.txt:478 (set): implicitly converting 'String' to 'STRING' type. This warning is for project developers. Use -Wno-dev to suppress it.
commit sha a910964ca18c3570a88f65043b0ad888ce13600e
tests: add support for LLVM 11.1
commit sha b1ef0c8a7bd433b81c057ecad656608a82a3b7dc
[Z3] Handle the case when interruption caught by Z3
commit sha 36780583dd78865100114b02627a3418b2d56deb
Add cmake custom target `uninstall` `make uninstall` is enabled. Without this, uninstalling was done manually with `rm` command.
commit sha 292600cf54d5fd73278f67a4f98c2f955cbdaa10
cmake: Fix CMP0026 policy deprecation warning CMake 3.19+ started to issue warnings if this policy is set to OLD: CMake Deprecation Warning at test/CMakeLists.txt:143 (cmake_policy): The OLD behavior for policy CMP0026 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD.
commit sha d309c4fa0ca2cd55e36cf1462b9057d6eb97a297
tests: Do not add klee tools to PATH in lit It may happen that some older instance of klee is already present in PATH. All tests that call plain klee instead of %klee may use it and then unexpectedly fail. This commit will make all tests that rely on klee tools being explicitly in PATH fail in our CI. From now on, only LLVM tools, FileCheck and not will be in lit's PATH.
commit sha b0aef8ebc9d53945549fc477558a4437baa46e2d
tests: Invoke tools through their corresponding macros
commit sha a0e2d3c837ddd4398ff3af76c34ddeb32d70e7b5
klee-replay: Fix -Wformat-truncation warning Increase the size of the buffer to PATH_MAX in create_link as that is the maximal possible length of fname and check whether output truncation occurred. Fixes: tools/klee-replay/file-creator.c: In function 'create_file': tools/klee-replay/file-creator.c:55:31: warning: '%s' directive output may be truncated writing up to 4095 bytes into a region of size 64 [-Wformat-truncation=] 55 | snprintf(buf, sizeof(buf), "%s.lnk", fname); | ^~ ...... 344 | target = tmpname; | ~~~~~~~ In file included from /usr/include/stdio.h:866, from tools/klee-replay/file-creator.c:16: /usr/include/bits/stdio2.h:70:10: note: '__snprintf_chk' output between 5 and 4100 bytes into a destination of size 64 70 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 71 | __bos (__s), __fmt, __va_arg_pack ()); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
commit sha 536f363587956ef1e59ecce4c932262ef57ff371
test/Concrete: Use Python 3 in ConcreteTest.py explicitly Some Linux distributions, e.g. Fedora, do not install the unversioned Python binary by default and Python 2 has been dead for more than a year.
commit sha 88893697f6630f0d281d21be6362489e616bca2f
Refactored MaxStatis*Pct conditions into a separate function.
commit sha c8ef08267fd5e67f40defac1ae692e8ec906fa3f
Added -max-static-pct-check-delay to replace the hardcoded delay after which the MaxStatic*Pct checks are performed.
commit sha 126387bc7921e892d4a5b75a8874242527cc8111
Added a warning when forking is skipped due to MaxStatic*Pct limits being reached
push time in 7 days
push eventlahiri-phdworks/klee
commit sha d14fa3e44768312f0117d35cec7f2a19322c3f15
Options to print PTREE Dump and States directly.
commit sha b7441d9b1ac70e97d3b06079b0b691383c1f67db
Custom ETREE for testing branches and forks in KLEE
commit sha 01db812556d55b98c6e16074be145505ee1f5b7b
Added ETree.h for Execution Tree Class
commit sha 8e221aa174ad57fe21b653505442112032814274
ETree.h, ETree.cpp implementation
commit sha 81102665f4a641e880d3835a9f9d7db5836c8726
ETree.h, ETree.cpp implementation
commit sha 62cc65ce85e14eeda8f972010410dd7aec9da860
Intergrate ETree Implementation
commit sha fc5a68d10ae906207eb671411ac98d561006ecde
Fixed class klee::ETree incomplete type error, by missing import
commit sha 5d8517542e39e6198a9541a0c4654b59ab5523f0
Fixed Issues with forkState() and other Integrations.
commit sha f926d22747a47ae061b55dbe482d2643a4346a8c
TODO : Add a Execution Node to current state
commit sha 780df6b4a22531e068148b0ab689214d78969b08
FIXME : Fork State
commit sha 41ddc8750c7d9ade6c0095bf7e9b4546f79f3fdd
Fixed Graph Output
commit sha b5bcd8143e79b6542eac6c42cc6d7b2ca4d16756
Visualize the transitions in State Graph
commit sha 1eb06502ab611a6db486600177547e53fd6702a0
Class for new Probabilistic States
commit sha c9d69aac752995202269489efe204f9ecda504e4
Class for new Probabilistic States
commit sha 01c30b9e1abe4771a330132ac7fe9fdce471585b
Merge pull request #2 from lahiri-phdworks/master Updating symbolic_tree branch from self:master
commit sha f6c86e59ab93a5f0beae95ef6dba028980ca2aa5
TODO : WIP Probabilistic State
commit sha 7d56595e9bea5917c6557eaa2fd2fb5d05da3bc4
Merge remote-tracking branch 'origin/symbolic_tree' into symbolic_tree
commit sha 93d6660c3d309ca292eaf93ec265ea67171e9ede
klee_make_pse_symbolic( ) implementation
commit sha 8075d5def7af8d456de38baeddaf9ab8a442d9f9
Linked ObjectState to ProbState
commit sha 01ac3202adc840ff3d66ea3b4996b901c85e979f
Update Memory.cpp
push time in 7 days
PR closed lahiri-phdworks/klee
Thank you for contributing to KLEE. We are looking forward to reviewing your PR. However, given the small number of active reviewers and our limited time, it might take a while to do so. We aim to get back to each PR within one month, and often do so within one week.
To help expedite the review please ensure the following, by adding an "x" for each completed item:
- [ ] The PR addresses a single issue. In other words, if some parts of a PR could form another independent PR, you should break this PR into multiple smaller PRs.
- [ ] There are no unnecessary commits. For instance, commits that fix issues with a previous commit in this PR are unnecessary and should be removed (you can find documentation on squashing commits here).
- [ ] Larger PRs are divided into a logical sequence of commits.
- [ ] Each commit has a meaningful message documenting what it does.
- [ ] The code is commented. In particular, newly added classes and functions should be documented.
- [ ] The patch is formatted via clang-format (see also git-clang-format for Git integration). Please only format the patch itself and code surrounding the patch, not entire files. Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
- [ ] Add test cases exercising the code you added or modified. We expect system and/or unit test cases for all non-trivial changes. After you submit your PR, you will be able to see a Codecov report telling you which parts of your patch are not covered by the regression test suite. You will also be able to see if the Github Actions CI and Cirrus CI tests have passed. If they don't, you should examine the failures and address them before the PR can be reviewed.
- [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.
pr closed time in 7 days
push eventlahiri-phdworks/klee
push time in 7 days
PR opened lahiri-phdworks/klee
Thank you for contributing to KLEE. We are looking forward to reviewing your PR. However, given the small number of active reviewers and our limited time, it might take a while to do so. We aim to get back to each PR within one month, and often do so within one week.
To help expedite the review please ensure the following, by adding an "x" for each completed item:
- [ ] The PR addresses a single issue. In other words, if some parts of a PR could form another independent PR, you should break this PR into multiple smaller PRs.
- [ ] There are no unnecessary commits. For instance, commits that fix issues with a previous commit in this PR are unnecessary and should be removed (you can find documentation on squashing commits here).
- [ ] Larger PRs are divided into a logical sequence of commits.
- [ ] Each commit has a meaningful message documenting what it does.
- [ ] The code is commented. In particular, newly added classes and functions should be documented.
- [ ] The patch is formatted via clang-format (see also git-clang-format for Git integration). Please only format the patch itself and code surrounding the patch, not entire files. Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
- [ ] Add test cases exercising the code you added or modified. We expect system and/or unit test cases for all non-trivial changes. After you submit your PR, you will be able to see a Codecov report telling you which parts of your patch are not covered by the regression test suite. You will also be able to see if the Github Actions CI and Cirrus CI tests have passed. If they don't, you should examine the failures and address them before the PR can be reviewed.
- [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.
pr created time in 7 days
push eventlahiri-phdworks/klee
commit sha 95f7f447432807efd70c8abac598d0d88ba1e9b1
test: count paths with -dump-states-on-halt=false
commit sha 78026968b7ee1abd97f39227ab7494a898c0d287
differentiate between partial and completed paths in summary and fix paths stats when not dumping states
commit sha 74ed0f5aa1b2b7fb1b42fa90ac0d7b3b4e0df85f
tests: adjust to new summary output
commit sha 41e84de8c64f15526f33e0b9769a9e6f0b861c44
cirrus: update FreeBSD python dependencies
commit sha c155cc7132a4d4bff042bf982ee08bf142a21b5e
extend function pointer test Part of the test was already disabled in the initial checkin. However, we do support function pointers if they are restricted to one or more possible values.
commit sha 24badb5bf17ff586dc3f1856901f27210713b2ac
allocate memory objects for functions Before, we reused the llvm::Function* value in the target program, even though it stems from KLEE's own address space. This leads to non-deterministic function pointers, even with --allocate-determ. This issue was identified in the MoKLEE paper. Now, we allocate a memory object per function, for its (potentially) deterministic address. Mapping this address back to llvm::Functions is done by the legalFunctions map. Also, pointer width now depends on the target, not the host.
commit sha 025abc7291dc492ae94df288030611e3d53afa35
Merge branch 'klee:master' into master
push time in 7 days
push eventlahiri-phdworks/klee
commit sha e17d5bc10b44c871922aa19eae4c05420329a2c3
WIP : KLEE Assume Printing
push time in a month
push eventlahiri-phdworks/klee
commit sha deae17c6ef4eec50160c62f122d27187847ef162
WIP : KLEE Assume Printing
push time in a month
push eventlahiri-phdworks/klee
commit sha 49b39918c399bc3a6083ae10127832e6d5d8a2f7
WIP : Select Instruction Dump : ITE
push time in a month
push eventlahiri-phdworks/klee
commit sha d470fcaf01ad6e1c087eec0e273bcbbc4891c968
WIP : State Expressions Dump
push time in a month
push eventlahiri-phdworks/klee
commit sha 53c1907336317f944bd948a68019747473a57831
WIP : Kquery Expression Dump Changes
push time in a month
push eventlahiri-phdworks/klee
commit sha dbe3e458d3e25fb092a5468a8fe551a6e7486aed
renaming 'libcxx' -> 'libc++'
commit sha 5f08b024bef12c3312d1e75f2c2ec5e5f5e0361f
add ifdefs for C++ exception handling restoring old behavior without EH support
commit sha b2157ca524c7c6ab8074f05b4c735a4fc237eb7d
add klee_messages for C++ exception handling support otherwise, it is hard to tell whether EH support is available or not
commit sha 5f8d562181bce7c0d11eae0a597e3f534966e42c
Executor: remove obsolete special case for __cxa_{re,}throw __cxa_throw and __cxa_rethrow were not handled by special function handlers in the final version of #966 (which introduced support for C++ exception handling)
commit sha 148a68df793fca84a36fefd8824ea54fdf6583f4
runtime/POSIX: fix failures with glibc-2.33 commit 8ed005daf0ab of glibc-2.33 (Remove stat wrapper functions, move them to exported symbols) removed renames of `__fxstat`, `__xstat`, and `__lxstat` to `__fxstat64`, `__xstat64`, and `__lxstat64`, respectively. But we relied on the renames to build `fd_64.c` properly. With glibc 2.33, we now see link failures of the POSIX runtime: error: Linking globals named '__xstat': symbol multiply defined! Rename the functions using `__REDIRECT_NTH` in the code as `__USE_FILE_OFFSET64` case (which we define at the top of the file by `#define _FILE_OFFSET_BITS 64`) did exactly that. Fixes #1384.
commit sha 295353010d23c9561826f811a59b7d5556c45596
Improved PR template by making it more succinct.
commit sha 91420b32cd347b43f64d337e5bd1f0855d0b247c
cmake: Fix warning about implicit type conversion Fixes: CMake Warning (dev) at CMakeLists.txt:478 (set): implicitly converting 'String' to 'STRING' type. This warning is for project developers. Use -Wno-dev to suppress it.
commit sha a910964ca18c3570a88f65043b0ad888ce13600e
tests: add support for LLVM 11.1
commit sha b1ef0c8a7bd433b81c057ecad656608a82a3b7dc
[Z3] Handle the case when interruption caught by Z3
commit sha 36780583dd78865100114b02627a3418b2d56deb
Add cmake custom target `uninstall` `make uninstall` is enabled. Without this, uninstalling was done manually with `rm` command.
commit sha 292600cf54d5fd73278f67a4f98c2f955cbdaa10
cmake: Fix CMP0026 policy deprecation warning CMake 3.19+ started to issue warnings if this policy is set to OLD: CMake Deprecation Warning at test/CMakeLists.txt:143 (cmake_policy): The OLD behavior for policy CMP0026 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD.
commit sha d309c4fa0ca2cd55e36cf1462b9057d6eb97a297
tests: Do not add klee tools to PATH in lit It may happen that some older instance of klee is already present in PATH. All tests that call plain klee instead of %klee may use it and then unexpectedly fail. This commit will make all tests that rely on klee tools being explicitly in PATH fail in our CI. From now on, only LLVM tools, FileCheck and not will be in lit's PATH.
commit sha b0aef8ebc9d53945549fc477558a4437baa46e2d
tests: Invoke tools through their corresponding macros
commit sha a0e2d3c837ddd4398ff3af76c34ddeb32d70e7b5
klee-replay: Fix -Wformat-truncation warning Increase the size of the buffer to PATH_MAX in create_link as that is the maximal possible length of fname and check whether output truncation occurred. Fixes: tools/klee-replay/file-creator.c: In function 'create_file': tools/klee-replay/file-creator.c:55:31: warning: '%s' directive output may be truncated writing up to 4095 bytes into a region of size 64 [-Wformat-truncation=] 55 | snprintf(buf, sizeof(buf), "%s.lnk", fname); | ^~ ...... 344 | target = tmpname; | ~~~~~~~ In file included from /usr/include/stdio.h:866, from tools/klee-replay/file-creator.c:16: /usr/include/bits/stdio2.h:70:10: note: '__snprintf_chk' output between 5 and 4100 bytes into a destination of size 64 70 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 71 | __bos (__s), __fmt, __va_arg_pack ()); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
commit sha 536f363587956ef1e59ecce4c932262ef57ff371
test/Concrete: Use Python 3 in ConcreteTest.py explicitly Some Linux distributions, e.g. Fedora, do not install the unversioned Python binary by default and Python 2 has been dead for more than a year.
commit sha 88893697f6630f0d281d21be6362489e616bca2f
Refactored MaxStatis*Pct conditions into a separate function.
commit sha c8ef08267fd5e67f40defac1ae692e8ec906fa3f
Added -max-static-pct-check-delay to replace the hardcoded delay after which the MaxStatic*Pct checks are performed.
commit sha 126387bc7921e892d4a5b75a8874242527cc8111
Added a warning when forking is skipped due to MaxStatic*Pct limits being reached
commit sha 458e3f9ec4f8d5d2711a0aeff7a532b184e7d075
Test for -max-static-fork-pct
commit sha e2cb581253b18b50d6526cc4a28ee7ff933a29bf
Refactored maxStaticPctChecks into a sequence of conditions.
push time in a month
PR merged lahiri-phdworks/klee
Thank you for contributing to KLEE. We are looking forward to reviewing your PR. However, given the small number of active reviewers and our limited time, it might take a while to do so. We aim to get back to each PR within one month, and often do so within one week.
To help expedite the review please ensure the following, by adding an "x" for each completed item:
- [x] The PR addresses a single issue. In other words, if some parts of a PR could form another independent PR, you should break this PR into multiple smaller PRs.
- [ ] There are no unnecessary commits. For instance, commits that fix issues with a previous commit in this PR are unnecessary and should be removed (you can find documentation on squashing commits here).
- [ ] Larger PRs are divided into a logical sequence of commits.
- [ ] Each commit has a meaningful message documenting what it does.
- [ ] The code is commented. In particular, newly added classes and functions should be documented.
- [x] The patch is formatted via clang-format (see also git-clang-format for Git integration). Please only format the patch itself and code surrounding the patch, not entire files. Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
- [ ] Add test cases exercising the code you added or modified. We expect system and/or unit test cases for all non-trivial changes. After you submit your PR, you will be able to see a Codecov report telling you which parts of your patch are not covered by the regression test suite. You will also be able to see if the Github Actions CI and Cirrus CI tests have passed. If they don't, you should examine the failures and address them before the PR can be reviewed.
- [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.
pr closed time in a month
PR opened lahiri-phdworks/klee
Thank you for contributing to KLEE. We are looking forward to reviewing your PR. However, given the small number of active reviewers and our limited time, it might take a while to do so. We aim to get back to each PR within one month, and often do so within one week.
To help expedite the review please ensure the following, by adding an "x" for each completed item:
- [ ] The PR addresses a single issue. In other words, if some parts of a PR could form another independent PR, you should break this PR into multiple smaller PRs.
- [ ] There are no unnecessary commits. For instance, commits that fix issues with a previous commit in this PR are unnecessary and should be removed (you can find documentation on squashing commits here).
- [ ] Larger PRs are divided into a logical sequence of commits.
- [ ] Each commit has a meaningful message documenting what it does.
- [ ] The code is commented. In particular, newly added classes and functions should be documented.
- [ ] The patch is formatted via clang-format (see also git-clang-format for Git integration). Please only format the patch itself and code surrounding the patch, not entire files. Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
- [ ] Add test cases exercising the code you added or modified. We expect system and/or unit test cases for all non-trivial changes. After you submit your PR, you will be able to see a Codecov report telling you which parts of your patch are not covered by the regression test suite. You will also be able to see if the Github Actions CI and Cirrus CI tests have passed. If they don't, you should examine the failures and address them before the PR can be reviewed.
- [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.
pr created time in a month
push eventlahiri-phdworks/klee
push time in a month
push eventlahiri-phdworks/klee
commit sha cf007d7ac56bec3ef1aade37261f80d2fff5a8b6
WIP : KLEE assume & Variable Symbolic Dump Improved.
push time in a month