-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Seg Fault seen in DTTSTheta::setConfig in production #44999
Comments
cms-bot internal usage |
A new Issue was created by @Dr15Jones. @makortel, @smuzaffar, @Dr15Jones, @rappoccio, @antoniovilela, @sextonkennedy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign L1Trigger/DTTriggerServerTheta |
New categories assigned: l1 @epalencia,@aloeliger you have been requested to review this Pull request/Issue and eventually sign? Thanks |
The full traceback is
|
The full log info can be found https://cernbox.cern.ch/files/link/public/CQvjzkONaprof65?tiles-size=1&items-per-page=100&view-mode=resource-table with file vocms0253.cern.ch-283595-0-log.tar.gz |
I see at least one (probably unrelated) bug in the code cmssw/L1Trigger/DTTrigger/src/DTTrig.cc Lines 227 to 231 in d376eb3
The use of |
So the code crashes in cmssw/L1Trigger/DTTriggerServerTheta/src/DTTSTheta.cc Lines 67 to 70 in d376eb3
where the only two possible bad pointers are |
So I used the configurations and ran them at FNAL on a local machine interactively and the jobs processed just fine. |
Production jobs running CMSSW_10_6_31 running SMP-RunIISummer20UL18wmLHEGEN for the step reading pileup mixing files is seg faulting in
DTTSTheta::setConfig(DTConfigManager const*)
The text was updated successfully, but these errors were encountered: