Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • nptool nptool
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • np
  • nptoolnptool
  • Issues
  • #25
Closed
Open
Issue created Feb 20, 2017 by Adrien Matta@matta☠Owner

Segfaults - currently for information only.

Created by: padsley

This issue has been created for my own benefit so I have a place to store my thoughts. As you were.

I am currently getting a segmentation violation sometimes.

If I run a calculation with the same inputs, sometimes when I do /run/beamOn N, it crashes.

The culprit is Target::SlowDownBeam, which, when the fault occurs, is doing its first call using G4ParticleDefinition* (this is line 252 in Target.cc where if(Beam->GetParticleName()=="neutron" appears.

The failure always comes at the first event which makes me think that something is going wrong in the initialisation.

If I comment out that line (252), then the code fails further down. Yay.

The failure is not consistent - i.e. it doesn't always happen. If I re-run with the same input, things are working fine.

Assignee
Assign to
Time tracking