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

Improve handling of deleted executable object files #65

Merged

Conversation

javierhonduco
Copy link
Owner

As before this commit, if lightswitch finds an object file that's been deleted, which are named as $original_name (deleted) we would return an error and never add the unwind information for any of the object files. We could see this for example in lightswitch as I assume some parts of the runtime could load the debuginfo file at runtime and then remove it at some point.

This commit also slighly improves the code/

Test Plan

Ran while running another lightswitch instance, the error is not showing up anymore.

As before this commit, if lightswitch finds an object file that's been
deleted, which are named as `$original_name (deleted)` we would return
an error and never add the unwind information for any of the object
files. We could see this for example in lightswitch as I assume some
parts of the runtime could load the debuginfo file at runtime and then
remove it at some point.

This commit also slighly improves the code/

Test Plan
=========

Ran while running another `lightswitch` instance, the error is not
showing up anymore.
@javierhonduco javierhonduco merged commit 6c5cec2 into main Sep 6, 2024
4 checks passed
@javierhonduco javierhonduco deleted the improve-handling-of-deleted-executable-object-files branch September 6, 2024 17:55
javierhonduco added a commit that referenced this pull request Sep 16, 2024
As before this commit, if lightswitch finds an object file that's been
deleted, which are named as `$original_name (deleted)` we would return
an error and never add the unwind information for any of the object
files. We could see this for example in lightswitch as I assume some
parts of the runtime could load the debuginfo file at runtime and then
remove it at some point.

This commit also slighly improves the code/

Test Plan
=========

Ran while running another `lightswitch` instance, the error is not
showing up anymore.
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.

1 participant