rust-lang / rust-lang/rust-bindgen

Build fails with (signal: 11, SIGSEGV: invalid memory reference)

Open
#2,035 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
5.3k
Forks
829
Avg merge
1d 1h
Merged PRs (30d)
15

Description

I had previously waited for https://github.com/rust-lang/rust-bindgen/issues/493 to be closed as I had hoped this would fix it for my case, a libfive wrapper, too.

However, it still persists:

error: failed to run custom build command for `libfive-sys v0.1.0 (/Users/moritz/code/crates/libfive-sys)`

Caused by:
  process didn't exit successfully: `/Users/moritz/code/crates/libfive-sys/target/debug/build/libfive-sys-8ef0dc6589c9b81d/build-script-build` (signal: 11, SIGSEGV: invalid memory reference)

The repository is here.
Requires --recursive cloning.
I am building on macOS. The README has instructions for dependencies.

I am only including libfive.h in my wrapper.hpp.

Libfive uses C++17 features. The previous version I tried to wrap, in January, was just using C++11 features. I.e. I doubt this is related.

Just run cargo build on latest nightly to reproduce.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Clone virtualritz/libfive-sys recursively on macOS, follow its README dependency instructions, and run cargo build on the latest nightly to reproduce the build-script-build SIGSEGV. Start with the wrapper.hpp inclusion of libfive.h and the generated build entry point. Done means the project builds without the invalid-memory-reference failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, rust
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.