DWARF: Fix debug_range handling of invalid entries (#2662)

If an invalid entry appears - either it began as such, or became
invalid after optimization - we should not emit (0, 0) which is
an end marker. Instead, emit an invalid entry marker, something
with (0, x) for x != 0.

As a bonus, if a test/passes case has "noprint" in the name,
don't print the wasm, which we do by default. In the testcase
here for example we just care about the dwarf, and the
printed module would be quite large.

Thank you to @paolosevMSFT for identifying and suggesting
the fix.

0 files changed, 0 insertions, 0 deletions