Skip to content
This repository was archived by the owner on May 31, 2022. It is now read-only.

Segfault when calling object.name() #25

Open
gz opened this issue Jul 5, 2019 · 0 comments
Open

Segfault when calling object.name() #25

gz opened this issue Jul 5, 2019 · 0 comments

Comments

@gz
Copy link

gz commented Jul 5, 2019

The following code leads to a segfault on MacOS

pub fn debug_topology() {
    let topo = Topology::new();
	for i in 0..topo.depth() {
		println!("*** Objects at level {}", i);

		for (idx, object) in topo.objects_at_depth(i).iter().enumerate() {
			println!("{}", object.name());
		}
	}
}

Program aborts with:

error: process didn't exit successfully: `/Users/gz/workspace/node-replication/target/release/deps/criterion_bench-398cce13a8a29333 --bench` (signal: 11, SIGSEGV: invalid memory reference)

lstopo version is:

$ lstopo --version
lstopo 1.11.5
@gz gz changed the title Segfault Segfault when calling object.name() Jul 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant