-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache the path on Module
for easier diagnostics
#106103
Conversation
Tagging subscribers to this area: @mangod9 |
Module
for eaiser diagnosticsModule
for easier diagnostics
SString works well for temporary values - method arguments, locals, etc. It works poorly as a field with longer lifetime that is potentially accessed by multiple threads (you have to be very careful how you use it to avoid subtle race conditions). I think it is a good idea to avoid exposing SString for the cdac |
@lambdageek You would think marking something |
Co-authored-by: Aleksey Kliger (λgeek) <akliger@gmail.com>
Re: lifetime and
|
a65c3ce
to
b2062d4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Long term, I'd like to see us stop using an SString as a field at all on PEImage, but we can do that some other time.
PEImage
take a path in its constructor and make its member constModule
I'm trying to avoid having to expose PEAssembly/PEImage in data descriptors to the cDAC just to get the module path.
Contributes to #99302
cc @lambdageek @davidwrighton