You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Jules Villard dbdf076e30 [pulse] take histories into account for all aspects of a report ... Summary: A previous change made pulse look into value histories for causes of invalidation in case the access trace of a value already contained the reason why that value is invalid, in order to save printing the invalidation trace in addition to the access trace. It also made reporting more accurate for null dereference as the source of null was often better identified (in cases where several values are null or zero). But, the history is also relevant to the bug type and the error message. Make these take histories into account too. Also fix a bug where we didn't look inside the sub-histories contained within function calls when looking for an invalidation along the history. Reviewed By: da319 Differential Revision: D28254334 fbshipit-source-id: 5ca00ee54		4 years ago
..
c	[pulse] resolve function pointers when known	4 years ago
c_cpp/pulse	[pulse] Loosen fieldname comparison in state	4 years ago
cpp	[pulse] take histories into account for all aspects of a report	4 years ago
dotnet	Infer# integration (#1361)	4 years ago
java	[pulse] take histories into account for all aspects of a report	4 years ago
objc	[pulse] no longer drop attributes of dead addresses	4 years ago
objcpp	[pulse] no longer drop attributes of dead addresses	4 years ago