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

Facilitate better backtraces in CI #12

Closed
wants to merge 51 commits into from
Closed

Conversation

hmenke
Copy link
Member

@hmenke hmenke commented Oct 6, 2023

No description provided.

Wentzell and others added 30 commits February 17, 2022 17:04
Co-authored-by: Dylan Simon <dylan@dylex.net>
Co-authored-by: Alexander Hampel <ahampel@flatironinstitute.org>
@@ -96,6 +97,8 @@ jobs:
- name: Test app4triqs
env:
DYLD_FALLBACK_LIBRARY_PATH: /usr/local/opt/llvm/lib
LD_PRELOAD: /usr/lib/x86_64-linux-gnu/libSegFault.so
Copy link
Member Author

Choose a reason for hiding this comment

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

Using libSegFault is debatable.

Copy link
Member

Choose a reason for hiding this comment

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

Would this have any implications in the absence of segfaults?

Copy link
Member Author

Choose a reason for hiding this comment

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

Essentially the entire constructor boils down to sigaction (SIGSEGV, &sa, NULL); where sa is the custom segfault handler. So in the absence of SIGSEGV this will still consume one additional slot on the signal stack and might clash or otherwise interact with other signal handlers, although I don't think that TRIQS uses POSIX signals for anything.

@hmenke
Copy link
Member Author

hmenke commented Nov 3, 2023

I've split the PR into multiple commits, so you can cherry-pick what you consider reasonable.

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.

5 participants