diff options
| author | Aleksey Kliger (λgeek) <alklig@microsoft.com> | 2022-02-25 16:57:38 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-25 16:57:38 +0300 |
| commit | 31bd72de7570200d46314683f6b556cdbebdd6e3 (patch) | |
| tree | e5df5776603b5cf02226b7962488be66e34dd3d0 /.devcontainer | |
| parent | e4dde6bacd91cb6364c3bf6a9c0df2ecfc1934d8 (diff) | |
[mono][hot reload] Fix sequence point logic for compiler-generated methods in updates (#65865)
* [tests] Pass PDB delta to ApplyUpdate
* extra tracing output
* Return 0 if a method has no sequence points
-1 means there was some kind of problem
0 means 0 sequence points
In particular for mono_ppdb_get_seq_points_enc a compiler-generated method might have 0 sequence points in the PDB delta, but we should consider that as ok, and not fall back to looking in the baseline image
* pass MONO_DEBUG=getn-seq-points to hot reload tests
For platforms where we use the remote executor, set the environment variable when starting the remote process.
For WASM, pass --setenv when building the project.
* fix whitespace
Diffstat (limited to '.devcontainer')
0 files changed, 0 insertions, 0 deletions