GEOS-DEV / GEOS-DEV/GEOS

In non-throw cases, the stack trace is misleading.

Open
#4,023 0 comments 0 reactions 3 assignees View on GitHub

@castelletto1 is already working on this.

Since Apr 8, 2026.

type: bug type: new
Dominant language
C++
Stars
287
Forks
109
Avg merge
4d 41m
Merged PRs (30d)
5

Description

Describe the bug
I am trying to find why a simulation that runs on CPU is crashing on GPU.

To Reproduce
I cannot provide the input file at this time.

Expected behavior
I expect the stack trace to indicate the location of the error. Instead I get this:

Functions: adding TableFunction equil_thickSand_hex_Elevation_index_table
***** Error
***** Rank 0
***** Message from before signal error output:
terminate called without an active exception

***** StackTrace of 25 frames
  - Frame  0:  geos::OutputStreamDeviation::flush(std::function<void (std::basic_string_view<char, std::char_traits<char> >, std::basic_string_view<char, std::char_traits<char> >)> const&, std::basic_string_view<char, std::char_traits<char> >) 
  - Frame  1:  /usr/workspace/settgast/Codes/geosx/GEOSX_develop/build-matrix-toss_4_x86_64_ib-gcc@13.3.1-cuda@12.9.1-release/lib/libcommon.so 
  - Frame  2:  /lib64/libc.so.6 
  - Frame  3:  gsignal 
  - Frame  4:  abort 
  - Frame  5:  /lib64/libstdc++.so.6 
  - Frame  6:  /lib64/libstdc++.so.6 
  - Frame  7:  /lib64/libstdc++.so.6 
  - Frame  8:  /usr/workspace/settgast/Codes/geosx/GEOSX_develop/build-matrix-toss_4_x86_64_ib-gcc@13.3.1-cuda@12.9.1-release/lib/libmesh.so 
  - Frame  9:  geos::CellElementSubRegion::~CellElementSubRegion() 
  - Frame 10:  geos::dataRepository::Group::~Group() 
  - Frame 11:  geos::dataRepository::Group::~Group() 
  - Frame 12:  geos::CellElementRegion::~CellElementRegion() 
  - Frame 13:  geos::dataRepository::Group::~Group() 
  - Frame 14:  geos::dataRepository::Group::~Group() 
  - Frame 15:  std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() 
  - Frame 16:  geos::MeshLevel::~MeshLevel() 
  - Frame 17:  geos::MeshLevel::~MeshLevel() 
  - Frame 18:  geos::dataRepository::Group::~Group() 
  - Frame 19:  geos::dataRepository::Group::~Group() 
  - Frame 20:  geos::MeshBody::~MeshBody() 
  - Frame 21:  geos::dataRepository::Group::~Group() 
  - Frame 22:  geos::dataRepository::Group::~Group() 
  - Frame 23:  geos::DomainPartition::~DomainPartition() 
  - Frame 24:  geos::dataRepository::Group::~Group() 
*****

***** ExternalError
***** Rank 0
***** Message from Signal (detected from Signal Handler):
Signal encountered (no. 6): Aborted

***** StackTrace of 25 frames
  - Frame  0:  /lib64/libc.so.6 
  - Frame  1:  gsignal 
  - Frame  2:  abort 
  - Frame  3:  /lib64/libstdc++.so.6 
  - Frame  4:  /lib64/libstdc++.so.6 
  - Frame  5:  /lib64/libstdc++.so.6 
  - Frame  6:  /usr/workspace/settgast/Codes/geosx/GEOSX_develop/build-matrix-toss_4_x86_64_ib-gcc@13.3.1-cuda@12.9.1-release/lib/libmesh.so 
  - Frame  7:  geos::CellElementSubRegion::~CellElementSubRegion() 
  - Frame  8:  geos::dataRepository::Group::~Group() 
  - Frame  9:  geos::dataRepository::Group::~Group() 
  - Frame 10:  geos::CellElementRegion::~CellElementRegion() 
  - Frame 11:  geos::dataRepository::Group::~Group() 
  - Frame 12:  geos::dataRepository::Group::~Group() 
  - Frame 13:  std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() 
  - Frame 14:  geos::MeshLevel::~MeshLevel() 
  - Frame 15:  geos::MeshLevel::~MeshLevel() 
  - Frame 16:  geos::dataRepository::Group::~Group() 
  - Frame 17:  geos::dataRepository::Group::~Group() 
  - Frame 18:  geos::MeshBody::~MeshBody() 
  - Frame 19:  geos::dataRepository::Group::~Group() 
  - Frame 20:  geos::dataRepository::Group::~Group() 
  - Frame 21:  geos::DomainPartition::~DomainPartition() 
  - Frame 22:  geos::dataRepository::Group::~Group() 
  - Frame 23:  geos::ProblemManager::~ProblemManager() 
  - Frame 24:  geos::GeosxState::~GeosxState() 
*****

Platform (please complete the following information):

  • Machine: LLNL/Matrix

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.