-
Notifications
You must be signed in to change notification settings - Fork 41
Segmentation fault in PulseCombiner::sumPulses caused by a hit with an exceptionally large time #2789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mhkim-anl
wants to merge
9
commits into
main
Choose a base branch
from
2788-segmentation-fault-in-pulsecombiner
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+16
−17
Open
Segmentation fault in PulseCombiner::sumPulses caused by a hit with an exceptionally large time #2789
Changes from 5 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
a16394e
Solve the segmentation fault issue
mhkim-anl 47d5589
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 2a2613d
Use size_t for size and index calculations
mhkim-anl 8d68013
Segmentation fault in PulseCombiner::sumPulses caused by a hit with a…
epic-capybara e8bbe2e
use auto when initializing with a cast to avoid duplicating the type …
mhkim-anl 78b042a
Merge branch 'main' into 2788-segmentation-fault-in-pulsecombiner
mhkim-anl 09bb1ab
Don't rely on maxStep being correct when filling combined pulse; Use …
mhkim-anl 01619aa
Merge branch 'main' into 2788-segmentation-fault-in-pulsecombiner
mhkim-anl f3416a7
Merge branch 'main' into 2788-segmentation-fault-in-pulsecombiner
mhkim-anl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is an implicit assumption for the correct operation of this function: that
pulsesis time-ordered (and has at least one entry). If that assumption is not guaranteed (in this case two frames away) this will start to return negative time differences. Can you make this a bit clearer in the name of this function, its documentation, and the calling context?Also, we calculate
(pulse.getTime() - pulses[0].getTime()) / pulses[0].getInterval()in two identical loops. In the first loop, it seems that all you calculate is actually:(where the
std::ranges::maxdoes not do worse than what you do, but is arguably clearer).