Conversation
krnowak
commented
Nov 29, 2023
Using strict mode install a trap handler that prints backtraces in case of errors. This will be useful to print some additional debugging information.
Recently we had some problems with read-only filesystems, that pop up in different places. It may be easier to catch if the debugging info is printed in an error case instead of just one specific location.
5fe2530 to
cc60a22
Compare
2 tasks
dongsupark
approved these changes
Feb 20, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a follow up to Kai's PR (#1401). It will print debugging output together with a backtrace now. In order to do it, the build_sysext is now using the strict mode too, which enable the backtraces to be printed.