-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
ASAN problem in CSCXonStrip_MatchGatti #32274
Comments
assign reconstruction |
A new Issue was created by @makortel Matti Kortelainen. @Dr15Jones, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
From the set of PRs merged since the previous ASAN builds (that did not have this error) #32052 could be the cause (the only one with "CSC" in its name, and it touches code in the same package. |
@nvoytish |
Can you clarify what we are looking for? Does this mean some dynamically assigned memory has been overwritten, or can it mean some simpler thing like a misaligned variable? I do not know what ASAN tests exactly. But the issue might be easier to track down if it could just be some value passed in to findXOnStrip is invalid. (That would seem more likely since the recent updates to the code can affect those.) |
The complaint is about a read (or write) beyond an allocated memory block. After a quick peek into the code I'd guess one of these array accesses goes out of bounds cmssw/RecoLocalMuon/CSCRecHitD/src/CSCXonStrip_MatchGatti.cc Lines 549 to 570 in dd492f7
So the problem could well be
|
Hi @slava77 ! |
@ptcox I managed to find what causes the problem. In a particular event the strip from one chamber (ME11A) is combined with a wire that it physically can not intersect (last wg from ME11B). This causes a mess in Gatti correction calculation. I'll try to understand which change in code lead to this. Sorry for the slow progress! |
That’s good progress! And something like I was expecting. Maybe something I missed in the intrinsic traps in the new code, and we still need some sort of ‘inside’ check.
… On Dec 2, 2020, at 11:31, nvoytish ***@***.***> wrote:
@ptcox I managed to find what causes the problem. In a particular event the strip from one chamber (ME11A) is combined with a wire that it physically can not intersect (last wg from ME11B). This causes a mess in Gatti correction calculation. I'll try to understand which change in code lead to this. Sorry for the slow progress!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I'll keep digging. You were right, when you said that Gatti corrections are "a pain") |
Hi all! We are trying to come up with a right fix for the bug. I was working on it today, but couple hours ago after a successful compile I tried to run "cmsenv" command and got: and |
IBs stay for about 2 weeks; it looks like 11-23 has expired. |
Hi all! It turned out that we need to keep the omitted "if" |
Yes, thanks! |
Fix of issue cms-sw#32274 caused by changes in PR cms-sw#32052
+1 I do not find the CSC-related error in https://cmssdt.cern.ch/SDT/html/cmssdt-ib/#/relVal/CMSSW_11_3/2020-12-16-2300?selectedArchs=slc7_amd64_gcc900&selectedFlavors=ASAN_X&selectedStatus=failed anymore (after #32442 was merged on Dec 15) |
This issue is fully signed and ready to be closed. |
Workflow 4.37 step 3 fails in CMSSW_11_2_ASAN_X_2020-11-23-2300 with
The text was updated successfully, but these errors were encountered: