[release/7.0] Fix FailFast logging message

[github-actions]

Backport of #75685 to release/7.0

/cc @eduardo-vp

Customer Impact

When the customer's app crashes due to an exception like access violation in an external native code, the customer doesn't get the crash address and error code in the event log entry (there is an x instead due to a bug). This change is a regression from .NET 6.

Testing

A function in an external native code file with a memory access crash was used by a managed app. In the Event Viewer app it could be found the logs with the correct information.

Risk

Very low, this change only involves formatting character for the FormatMessage Windows API from a wrong one that doesn't format the values to a correct one and adds 0x prefix.

[ghost]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[carlossanlop]

@eduardo-vp what branch are you trying to target? Do you want this change backported to RC2 or to GA?

• If GA, then this branch is fine.
• But if you want the change to go to RC2, you need to close this and resubmit the /backport command but targeting the release/7.0-rc2 branch.

[janvorli]

@carlossanlop I think that GA is ok for this.

[carlossanlop]

Thanks @janvorli for the confirmation. Since this is GA, can one of you please fill the template, then send an email to Tactics for approval?

[janvorli]

Yes, @eduardo-vp will do that.

[jeffschwMSFT]

approved. we will take for consideration in RC2. Can you take a look at the ci failures and get a code review?

[carlossanlop]

Approved via email by Tactics.

[carlossanlop]

CI green. Approved and signed off. Ready to merge.