DotnetRuntime provider needs to handle WCHAR strings

[LakshanF]

Currently the dotnetruntime provider doesn't correctly handle WCHAR strings. For example, the EventPipeWriteEventExceptionThrown_V1 will not print the correct values for the exception type and message. The Windows EtwProvider correctly handles this case.

This issue should wait for the likely refactoring that will happen when fixing #87445.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Currently the dotnetruntime provider doesn't correctly handle WCHAR strings. For example, the EventPipeWriteEventExceptionThrown_V1 will not print the correct values for the exception type and message. The Windows EtwProvider correctly handles this case.

This issue should wait for the likely refactoring that will happen when fixing #87445.

Author:	LakshanF
Assignees:	LakshanF
Labels:	area-NativeAOT-coreclr
Milestone:	8.0.0

[elinor-fung]

I think this just needs a version of WriteToBuffer for const WCHAR* strings. It's currently calling the template function, which won't compute the byte count like we want for strings:

runtime/src/coreclr/nativeaot/Runtime/eventpipe/dotnetruntime.cpp

Lines 39 to 51 in f9f7f80

	template <typename T>
	bool WriteToBuffer(const T &value, BYTE *&buffer, size_t& offset, size_t& size, bool &fixedBuffer)
	{
	if (sizeof(T) + offset > size)
	{
	if (!ResizeBuffer(buffer, size, offset, size + sizeof(T), fixedBuffer))
	return false;
	}
	memcpy(buffer + offset, (char *)&value, sizeof(T));
	offset += sizeof(T);
	return true;
	}

[LakshanF]

@elinor-fung's above PR (#88365) fixes this and was incorporated into PR #87785 which was merged.