[release/7.0-preview2][mono][hot reload] Fix sequence point logic for compiler-generated methods in updates (#65867)v7.0.0-preview.2.22152.2release/7.0-preview2

* [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

* [debug] Handle gen-seq-points, and hot reload updates without PDBs

When hot reload is used with dotnet watch, the baseline PDBs are available, and
sequence points are enabled, but there are no PDB updates.

* [hot_reload] Fix off by one error

when counting added and modified rows

* [hot_reload] Allow custom attribute deletions, even without ChangeCustomAttributes capability

Roslyn seems to delete nullability annotations sometimes

* Add regression test for adding static lambdas

* param attributes for hot reload

* don't run test where it isn't supported

0 files changed, 0 insertions, 0 deletions