mrigger

4 ms·

1.
GrayC: Greybox Fuzzing of Compilers and Analysers for C(github.com)
4 points by mrigger 3y ago|0 comments
2.
Encrypted Databases Made Secure yet Maintainable(github.com)
2 points by mrigger 3y ago|2 comments
3.
Dynamic Data-Race Prediction: Fundamentals, Theory and Practice (3 Hours Video)(youtube.com)
1 points by mrigger 4y ago|0 comments
4.
by mrigger 4y ago
More information at https://modus-continens.com/ .
5.
Modus: A language for building Docker/OCI container images(github.com)
56 points by mrigger 4y ago|28 comments
6.
DuckDB Testing – Present and Future(youtube.com)
1 points by mrigger 4y ago|0 comments
7.
Linear-Time Temporal Logic Guided Greybox Fuzzing(github.com)
1 points by mrigger 4y ago|0 comments
8.
YouTube Interviewing Series on Getting Faculty Positions in Computer Science(youtube.com)
1 points by mrigger 5y ago|0 comments
9.
Interview Questions for Computer Science Faculty Jobs(csfaculty.github.io)
1 points by mrigger 6y ago|0 comments
10.
Graalphp: An Efficient PHP Implementation Built on GraalVM(github.com)
113 points by mrigger 6y ago|56 comments
11.
by mrigger 6y ago
From the report at https://abertschi.ch/default_public/ethz/graalphp/download.p... : "Experimental results indicate that our runtime reaches competitive results with performance gains of up to 859% compar
12.
by mrigger 6y ago
For DBMS, the authors of the APOLLO system found the following [1]: "Code coverage is a frequently used feedback mechanism in fuzzing engines [22, 27]. We found that this metric is not particularly useful for fuzzing DBMSs, since the c
13.
by mrigger 6y ago
Yes, you are right, the results are not comparable between DBMS that we tested. For MySQL, the large number of existing bugs prevented us from going further, and also testing more advanced functionality (like FTS). For SQLite (and DuckDB),
14.
by mrigger 6y ago
I believe that the approaches that we designed could be implemented/extended to document-oriented DBMS. Since I don't have any experience with those DBMS, I have no intuition on whether the approaches would uncover any bugs. Imple
15.
by mrigger 6y ago
Thanks for your interest! I'd love to test H2, but we are currently lacking the resources to do so. We've received a number of similar requests in the last couple of days and weeks. For each DBMS that we test, we need to add some
16.
by mrigger 6y ago
Thanks! Here is one interesting example of a bug that was reported on the SQLite mailing list: https://www.mail-archive.com/sqlite-users@mailinglists.sqlit... . The SQL query that triggers the bug is rather complex. Interest
17.
by mrigger 6y ago
We automatically generate databases and queries. The main challenge is to verify that the query yields the expected result. To this end, we have designed and implemented three different approaches: * Pivoted Query Synthesis (PQS): The main
18.
by mrigger 6y ago
Thanks a lot! So far, we have considered only systems that are (partially) available in the open. Two of these are mainly developed commercially, namely CockroachDB and TiDB. We are glad that Cockroach Labs and PingCAP were indeed quite tha
19.
by mrigger 6y ago
Thank you! SQLite was indeed a challenging target. We could find and report many bugs in it only because all of our bugs were addressed very quickly (typically within a day). For some of the other DBMS that we tested, bugs were fixed slowly
20.
by mrigger 6y ago
Many DBMS development teams use SQLsmith and other random query generators, which can effectively find crash bugs. In contrast, we designed and developed SQLancer to automatically find logic bugs, which are bugs that cause the DBMS to compu