llnl / llnl/MemAxes

Unexpected exit when changing "Cluster Aggregates" in Single Axis section

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
22
Forks
5
PR merge metrics
No merged PRs in 30d

Description

When I was trying to change the depth to some number other than 0 in "Cluster Aggregates" in the Single Axis section, program exited with a bug report:

Process: MemAxes [4114]
Path: /Users/USER/*/MemAxes.app/Contents/MacOS/MemAxes
Identifier: ???
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: MemAxes [4114]
User ID: 501

Date/Time: 2015-10-12 02:18:25.989 -0700
OS Version: Mac OS X 10.11 (15A284)
Report Version: 11
Anonymous UUID: 5028DC7D-5B3D-4144-90D7-CE5204A8E2A6

Sleep/Wake UUID: 9995E98F-551A-4A89-8A90-D6FD98F5212E

Time Awake Since Boot: 120000 seconds
Time Since Wake: 5700 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
terminating with uncaught exception of type std::out_of_range: vector
abort() called

Contributor guide

No contributing guide indexed for this repository

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

No source file, test, or entry point is identified in the issue. Reproduce the crash by changing the depth from 0 in “Cluster Aggregates” under the Single Axis section, then trace the uncaught std::out_of_range exception; done means that changing the depth no longer exits MemAxes.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
data-visualization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.