miniblog.

← Back to all posts
Nov 27, 2015 at 10:44
Achievement unlocked: created a segfault using only safe @rustlang code!
Segfault in safe Rust when compiling with optimisations · Issue #30081 · rust-lang/rust
Segfault in safe Rust when compiling with optimisations · Issue #30081 · rust-lang/rust
#![feature(box_syntax, box_patterns)] use std::num::Wrapping; #[derive(Debug, Clone)] pub enum Instruction { Increment { amount: Wrapping<i8>, }, Loop(Vec<Box<Instruction>>), } /// Defines a method...

Related Posts

Jan 31, 2024 at 06:42
@skybert@emacs.ch Difftastic has very little unsafe, just the FFI to tree-sitter libraries. That said, I've actually seen safe Rust segfault in the past!
Segfault in safe Rust when compiling with optimisations · Issue #30081 · rust-lang/rust
Segfault in safe Rust when compiling with optimisations · Issue #30081 · rust-lang/rust
#![feature(box_syntax, box_patterns)] use std::num::Wrapping; #[derive(Debug, Clone)] pub enum Instruction { Increment { amount: Wrapping<i8>, }, Loop(Vec<Box<Instruction>>), } /// Defines a method...
Jan 30, 2024 at 06:09
Difftastic is written in Rust, so I was surprised to get a user report of a segfault. After some investigation, it turns out that it's a segfault in git itself, which has existed since 2014! https://lore.kernel.org/git/CAFXAjY7XcL1APhLRXU8TO96z=f7957f2ieK56dHVsXUay55vpg@mail.gmail.com/T/#u (Upstream has already kindly written a patch.)
Making sure you're not a bot!
Aug 6, 2018 at 07:53
It's possible to reliably segfault Emacs when using undercover, at least on Travis: https://github.com/Wilfred/elisp-def/commit/57523ad268e0f4d2550386d45d55d7a6ed5fe50c Not sure why at this point.
Increase execution limits to try to fix segfault · Wilfred/elisp-def@57523ad
Increase execution limits to try to fix segfault · Wilfred/elisp-def@57523ad
Find Emacs Lisp definitions. Contribute to Wilfred/elisp-def development by creating an account on GitHub.