You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the execution of my overridden getCalleeTarget(), I use the PA to look up the receiver of a method in one of the (duplicate) classes that reside in different files. I get back instances of both classes, although self can never refer to an instance of the other (duplicate) class.
The only thing I could think about was that perhap the call stack was too long. Every call gets its own node with a call string context of seemingly length 1. But, I failed to come up with a reproducible simple test cases that exercises this behavior, even after lengthening the call stack. This case is pretty complicated with a fair amount of lexical scoping if you look at the callers of the method.
In the end, I wind up with a set of two instances for the pointer key for self, one of which represents a class in a different file.
What I am seeing with Python is that there is a class with the same name (in fact, it's the exact same class copied) in two different files:
During the execution of my overridden
getCalleeTarget()
, I use the PA to look up the receiver of a method in one of the (duplicate) classes that reside in different files. I get back instances of both classes, althoughself
can never refer to an instance of the other (duplicate) class.This situation sounds like a bug to me more so than imprecision, and I am surprised to see it because we have added the full path to the CGNode names, for example:
The only thing I could think about was that perhap the call stack was too long. Every call gets its own node with a call string context of seemingly length 1. But, I failed to come up with a reproducible simple test cases that exercises this behavior, even after lengthening the call stack. This case is pretty complicated with a fair amount of lexical scoping if you look at the callers of the method.
In the end, I wind up with a set of two instances for the pointer key for
self
, one of which represents a class in a different file.Originally posted by @khatchad in #1417 (reply in thread)
The text was updated successfully, but these errors were encountered: