aarzilli 92faa95bf9 proc/stack: use BP when FDE is not available ... On Windows we can sometimes encounter threads stopped in locations for which we do not have entries in debug_frame. These cases seem to be due to calls to Windows API in the go runtime, we can still produce a (partial) stack trace in this circumstance by following frame pointers (starting with BP). We still prefer debug_frame entries when available since go functions do not have frame pointers before go1.8.		2017-02-22 20:39:28 +01:00
..
cmd	Replaced net/rpc with custom version	2016-07-02 12:16:06 +02:00
common_test.go	proc: Improvements to Variable printing (#444)	2016-04-24 10:15:39 -07:00
integration1_test.go	Move top-level packages into pkg	2017-02-08 12:17:19 -08:00
integration2_test.go	proc/stack: use BP when FDE is not available	2017-02-22 20:39:28 +01:00
variables_test.go	Move top-level packages into pkg	2017-02-08 12:17:19 -08:00