Ryan Liptak 95c43e20b4 Windows: Fix incorrect output when .pdb file is not found during stack trace
This `pdb.Pdb.init` call can return `error.FileNotFound`, which was previously resulting in:

    Unable to print stack trace: FileNotFound

which also aborts the stack trace printing (so any deeper stack traces are not printed).

It makes more sense to treat it as `MissingDebugInfo` which then gets printed as:

    ???:?:?: 0x7fffa8817033 in ??? (???)

and allows the stack trace to continue printing.

Note: locally, the error.FileNotFound was being triggered for me when looking for kernel32.pdb and ntdll.pdb
2022-08-22 20:51:55 -04:00
..
2022-08-21 16:42:11 +02:00
2022-08-09 16:19:55 +03:00
2022-08-22 14:07:22 +03:00
2022-08-19 16:45:16 -07:00
2022-05-13 16:43:59 -04:00
2022-04-20 17:18:06 -07:00
2022-01-07 00:06:06 -05:00
2022-06-03 20:21:20 +03:00
2022-04-14 10:12:45 -07:00
2022-07-09 15:19:03 +03:00
2022-05-26 21:58:19 -07:00
2022-04-15 17:01:01 -05:00
2022-01-07 00:06:06 -05:00
2022-08-18 18:58:28 -07:00