Skip to content
This repository was archived by the owner on Jan 11, 2024. It is now read-only.

Fix dumping stack from test coredumps on Linux - #1948

Merged
danmoseley merged 2 commits into
dotnet:masterfrom
danmoseley:runner
Mar 7, 2018
Merged

Fix dumping stack from test coredumps on Linux#1948
danmoseley merged 2 commits into
dotnet:masterfrom
danmoseley:runner

Conversation

@danmoseley

@danmoseley danmoseley commented Mar 7, 2018

Copy link
Copy Markdown
  • The dumps were in $EXECUTION_DIR. Pushd to that to find them.
  • Corerun is someplace else. Use $RUNTIME_PATH/dotnet instead. It's what we actually ran, anyway.
  • Add random suffix to keep more than one old dump

Tested locally by using kill -SIGABRT on running tests.

Fixes https://github.com/dotnet/corefx/issues/27818

@danmoseley
danmoseley requested review from Anipik and stephentoub March 7, 2018 22:35
@danmoseley
danmoseley merged commit 8bfc031 into dotnet:master Mar 7, 2018
@danmoseley
danmoseley deleted the runner branch March 7, 2018 23:41
@stephentoub

Copy link
Copy Markdown
Member

Now we wait...

@stephentoub

Copy link
Copy Markdown
Member

Initial results:
dotnet/corefx#27899 (comment)

Looks like we need gdb installed onto several of the images, and core dumps enabled on others. But RedHat and CentOS got the expected results :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"Unable to find corerun" when trying to crack dump on Helix machine

3 participants