ZigRazor / ZigRazor/CXXGraph

Segmentation fault while running benchmark_exe

Open
#352 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug core good first issue hacktoberfest Priority:Medium
Dominant language
C++
Stars
729
Forks
147
Avg merge
19h
Merged PRs (30d)
1

Description

Describe the bug
I am getting a Segmentation fault while running benchmark_exe.

To Reproduce
Steps to reproduce the behavior:

  1. following the given steps at Benchmark Execution
  2. run ./benchmark_exe

Expected behavior
the complete benchmark_exe should execute.

Screenshots

[user@fedora benchmark]$ ./benchmark_exe 
2023-09-26T22:54:46+05:30
Running ./benchmark_exe
Run on (8 X 4200 MHz CPU s)
CPU Caches:
  L1 Data 48 KiB (x4)
  L1 Instruction 32 KiB (x4)
  L2 Unified 1280 KiB (x4)
  L3 Unified 8192 KiB (x1)
Load Average: 0.93, 0.59, 0.45
***WARNING*** CPU scaling is enabled, the benchmark real time measurements may be noisy and will incur extra overhead.
***WARNING*** Library was built as DEBUG. Timings may be affected.
----------------------------------------------------------------------------------
Benchmark                                        Time             CPU   Iterations
----------------------------------------------------------------------------------
BFS_X/1                                       3698 ns         3693 ns       189718
BFS_X/18                                     29347 ns        29302 ns        24008
BFS_X/324                                   491839 ns       491235 ns         1401
BFS_X/5832                                 9127946 ns      9102094 ns           75
BFS_X/104976                             273177336 ns    272093218 ns            3
BFS_X/262144                             287219843 ns    286424086 ns            3
Segmentation fault (core dumped)

Desktop (please complete the following information):

  • OS: Fedora Linux 38 (Workstation Edition) 64bit
  • Version: 38

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

Start with the Benchmark Execution steps in the repository README and run ./benchmark_exe using the reported Fedora setup. The failure occurs after the BFS_X benchmark cases shown in the report; trace that execution to identify the crashing operation. Done means the complete benchmark_exe finishes without a segmentation fault and the relevant benchmark behavior is covered or verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.