Add SHA-384 and SHA-512 hash algorithm support for PDB checksums

[Copilot]

PDB files can specify document checksums using SHA-384 or SHA-512 per the Portable PDB spec. TraceEvent currently only recognizes MD5, SHA-1, and SHA-256.

Changes

Added GUID constants for the new algorithms:

• SHA-384: d99cfeb1-8c43-444a-8a6c-b61269d2a0bf
• SHA-512: ef2d1afc-6550-46d6-b14b-d70afe9a5566

Updated hash algorithm instantiation in three locations:

• PortableSymbolModule.cs - Portable PDB document handling
• NativeSymbolModule.cs - Native PDB managed source checksum handling
• SymbolReader.cs - ChecksumAlgorithm property type checks

All changes follow the existing pattern used for SHA-1 and SHA-256:

else if (hashAlgorithmGuid == HashAlgorithmSha384)
{
    _hashAlgorithm = System.Security.Cryptography.SHA384.Create();
}
else if (hashAlgorithmGuid == HashAlgorithmSha512)
{
    _hashAlgorithm = System.Security.Cryptography.SHA512.Create();
}

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add support for SHA-384 and SHA-512 algorithms used in PDB</issue_title>
<issue_description>Guids for the new algorithms are:

SHA-384: d99cfeb1-8c43-444a-8a6c-b61269d2a0bf
SHA-512: ef2d1afc-6550-46d6-b14b-d70afe9a5566

See https://github.com/dotnet/runtime/blob/main/docs/design/specs/PortablePdb-Metadata.md#document-table-0x30</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add support for SHA-384 and SHA-512 algorithms used in PDB #2365

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[brianrob]

@tmat do these new GUIDs apply to native PDBs (Windows) or just portable PDBs?

[tmat]

Both native and portable

[brianrob]

Great. Thanks. We'll get this merged.