Skip to content

Issues: bblum/landslide

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

10 Open 2 Closed
10 Open 2 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

bochs crash on setup on certain machines, not on others
#12 opened Dec 26, 2018 by bblum
import-p2.sh should make clean after rsyncing
#11 opened Dec 26, 2018 by bblum
yield() loop unblocking detection needs to check for kernel scheduler runnability if loop cares about yield return value
#10 opened Dec 26, 2018 by bblum
make quicksand detect compile errors by forking a separate program before any actual landslides, don't use message passing and get stuck like a big dummy
#9 opened Oct 4, 2018 by bblum
stack trace or read memory should check for cross page accesses and not blow up bochs if so
#8 opened Aug 21, 2018 by bblum
top level 'landslide' script check for exec2obj pointer fails to check substrings
#7 opened Jul 29, 2018 by bblum
have quicksand print something better than "you survived" when maximal ss verified
#6 opened Jul 23, 2018 by bblum
formalize quicksand's ability to ignore all the thread library functions as a cmdline option, like "don't test thrlib"
#3 opened Apr 28, 2018 by bblum
"page fault" error message should be "seg fault" for p2s/psus
#2 opened Apr 27, 2018 by bblum
410user/inc/thread.h should not include thr_internals.h (at least for PSU)
#1 opened Apr 27, 2018 by bblum
ProTip! Type g i on any issue or pull request to go back to the issue listing page.