21be59469a
Caching the frame in variablesByTag is problematic: 1. accounting for variables that are (partially) stored in registers is complicated (see issue #1106) 2. for some types (strings, interfaces...) simply creating the Variable object reads memory, which therefore happens before we can do any caching. Instead cache the entire frame when the EvalScope object is created. The cached range is between the SP value of the current frame and the CFA of the preceeding frame, if available, or the CFA of the current frame otherwise. Fixes #1106 |
||
|---|---|---|
| .. | ||
| debugger_darwin.go | ||
| debugger_linux.go | ||
| debugger_windows.go | ||
| debugger.go | ||
| locations_test.go | ||
| locations.go | ||