Skip to content

Conversation

@elinor-fung
Copy link
Member

Add an overload of WriteToBuffer specifically for handling const WCHAR* (treating it as a string instead of a single value).

Tested manually by taking the part of #87785 for ExceptionThrown_V1 (existing events before that PR don't have values of interest).

@LakshanF feel free to roll this into your PR and get rid of this one if you want

Fixes #87978

@ghost
Copy link

ghost commented Jul 4, 2023

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

Issue Details

Add an overload of WriteToBuffer specifically for handling const WCHAR* (treating it as a string instead of a single value).

Tested manually by taking the part of #87785 for ExceptionThrown_V1 (existing events before that PR don't have values of interest).

@LakshanF feel free to roll this into your PR and get rid of this one if you want

Fixes #87978

Author: elinor-fung
Assignees: -
Labels:

area-NativeAOT-coreclr

Milestone: -

@LakshanF
Copy link
Contributor

LakshanF commented Jul 5, 2023

I will close this PR and pull in this code to PR #87785 as you suggested, thanks!

@LakshanF LakshanF closed this Jul 5, 2023
@elinor-fung elinor-fung deleted the fix87978 branch July 5, 2023 23:38
@ghost ghost locked as resolved and limited conversation to collaborators Aug 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DotnetRuntime provider needs to handle WCHAR strings

2 participants