Skip to content
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

Various fixes #410

Merged
merged 16 commits into from
Dec 12, 2019
Merged

Various fixes #410

merged 16 commits into from
Dec 12, 2019

Conversation

nxtn
Copy link
Contributor

@nxtn nxtn commented Dec 11, 2019

No description provided.

@nxtn nxtn force-pushed the linux branch 4 times, most recently from c2bbb1c to 99ee35a Compare December 11, 2019 21:13
@leculver
Copy link
Contributor

Looks great so far. Thanks for tackling this.

@nxtn
Copy link
Contributor Author

nxtn commented Dec 12, 2019

Only PdbTests.PdbEqualityTest fails now.

@nxtn nxtn marked this pull request as ready for review December 12, 2019 12:03
@nxtn
Copy link
Contributor Author

nxtn commented Dec 12, 2019

Enabling PR status checks should be as simple as installing Azure Pipelines and granting it access to the repo. We'll soon be ready for full CI testing.

dt.BinaryLocator = new SymbolServerLocator("");
return dt;
if (RuntimeInformation.IsOSPlatform(OSPlatform.Windows))
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe I should remove "LoadCoreDump/LoadCrashDump" and just publish "LoadDump" and have the right reader selected based on either the operating system or the header of the file itself. (The latter gets complicated because DbgEngDataReader allows for .zip and .cab files too, which is useful for internal Microsoft developers.)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In fact, some functionalities are still available for LoadCoreDump on Windows, which don't request information from DAC.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. I'll leave this as-is for now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LoadCoreDump behaved well when I was working on #349 by experimenting with a coredump on Windows, but it won't work now because it throws after #393. Maybe we can throw that exception later when DAC is required.

{
value = Unsafe.As<byte, T>(ref buffer[0]);
value = Unsafe.As<byte, T>(ref MemoryMarshal.GetReference(buffer));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah right. Thanks for these cleanups. I'm still getting used to Unsafe.As and MemoryMarshal after being stuck on an older version of Desktop .Net for years.

@leculver leculver merged commit cd25920 into microsoft:master Dec 12, 2019
@nxtn nxtn deleted the linux branch December 12, 2019 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants