Our great sponsors
MPI.jl | rr | |
---|---|---|
3 | 100 | |
359 | 8,607 | |
1.9% | 1.0% | |
8.0 | 9.6 | |
27 days ago | 7 days ago | |
Julia | C++ | |
The Unlicense | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MPI.jl
-
Parallélisation distribuée presque triviale d’applications GPU et CPU basées sur des Stencils avec…
GitHub - JuliaParallel/MPI.jl: MPI wrappers for Julia
- Why Fortran is easy to learn
-
MPI and HPC libraries
I have actually had good success with Julia for this: https://github.com/JuliaParallel/MPI.jl. I acknowledge this community may not appreciate me sharing that.
rr
- Rr: Lightweight Recording and Deterministic Debugging
-
Deep Bug
Interesting. Perhaps you can inspect the disassembly of the function in question when using Graal and HotSpot. It is likely related to that.
Another debugging technique we use for heisenbugs is to see if `rr` [1] can reproduce it. If it can then that's great as it allows you to go back in time to debug what may have caused the bug. But `rr` is often not great for concurrency bugs since it emulates a single-core machine. Though debugging a VM is generally a nightmare. What we desperately need is a debugger that can debug both the VM and the language running on top of it. Usually it's one or the other.
> In general I’d argue you haven’t fixed a bug unless you understand why it happened and why your fix worked, which makes this frustrating, since every indication is that the bug exists within proprietary code that is out of my reach.
Were you using Oracle GraalVM? GraalVM community edition is open source, so maybe it's worth checking if it is reproducible in that.
-
So you think you want to write a deterministic hypervisor?
https://rr-project.org/ had the same problem. They use the retired conditional branch counter instead of instruction counter, and then instruction steeping until at the correct address.
-
Is Something Bugging You?
That'll work great for your Distributed QSort Incorporated startup, where the only product is a sorting algorithm.
Formal software verification is very useful. But what can be usefully formalized is rather limited, and what can be formalized correctly in practice is even more limited. That means you need to restrict your scope to something sane and useful. As a result, in the real world running thousands of tests is practically useful. (Well, it depends on what those tests are; it's easy to write 1000s of tests that either test the same thing, or only test the things that will pass and not the things that would fail.) They are especially useful if running in a mode where the unexpected happens often, as it sounds like this system can do. (It's reminiscent of rr's chaos mode -- https://rr-project.org/ linking to https://robert.ocallahan.org/2016/02/introducing-rr-chaos-mo... )
-
When "letting it crash" is not enough
The approach of check-pointing computation such that it is resumable and restartable sounds similar to a time-traveling debugger, like rr or WinDbg:
https://learn.microsoft.com/windows-hardware/drivers/debugge...
- When I got started I debugged using printf() today I debug with print()
- Rr: Record and Replay Debugger – Reverse Debugger
- OpenBSD KDE Plasma Desktop
-
Firefox 118
> I've heard Linux support was down to like one guy [...]
Linux support is down to you. It's down to all of us. Install rr (https://rr-project.org/) and capture a crash with it.
Then you can replay the crash, find out that it's actually crashing in your closed-source graphics driver, which will motivate you to switch to an open source driver and fix your issue.
Also, while you're at it, update your linux kernel and wayland. They've both had bugs that could manifest as random firefox crashes in the last several months.
- A Modern C Development Environment
What are some alternatives?
ImplicitGlobalGrid.jl - Almost trivial distributed parallelization of stencil-based GPU and CPU applications on a regular staggered grid
CodeLLDB - A native debugger extension for VSCode based on LLDB
DataFrames.jl - In-memory tabular data in Julia
gef - GEF (GDB Enhanced Features) - a modern experience for GDB with advanced debugging capabilities for exploit devs & reverse engineers on Linux
Makie.jl - Interactive data visualizations and plotting in Julia
rrweb - record and replay the web
SciMLBenchmarks.jl - Scientific machine learning (SciML) benchmarks, AI for science, and (differential) equation solvers. Covers Julia, Python (PyTorch, Jax), MATLAB, R
Module Linker - browse modules by clicking directly on "import" statements on GitHub
CUDA.jl - CUDA programming in Julia.
nbdev - Create delightful software with Jupyter Notebooks
Fortran-code-on-GitHub - Directory of Fortran codes on GitHub, arranged by topic
clog-cli - Generate beautiful changelogs from your Git commit history