Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • athena athena
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Jira
    • Jira
  • Merge requests 195
    • Merge requests 195
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • atlas
  • athenaathena
  • Merge requests
  • !22969

Merged
Created Apr 25, 2019 by Charles Burton@cburtonDeveloper

Prevent segfault for bad group name

  • Overview 7
  • Commits 1
  • Pipelines 1
  • Changes 1

Users who had a mismatch between the group name when the group is configured in the python and the group name when the fill() function is called. The existing check for an empty was not being used, since the [] operator on the GaudiHandleArray was returning a nullptr for non-existant elements of the array. I now check for a nullptr and offer a useful warning.

Users are now presented with the following.

FATAL The tool ExampleMonitor1 could not be found in the monitoring algorithm's tool array. This probably reflects a difference between your python configuration and c++ filling code.

Resolution for https://its.cern.ch/jira/browse/ATLASDQ-713.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: master-mongroup-segfault