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.

Sign up for GitHub

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

Jump to bottom

Do not attach gdb by default #90

Closed
tmadlener opened this issue Nov 28, 2022 · 1 comment
Closed

Do not attach gdb by default #90

tmadlener opened this issue Nov 28, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@tmadlener
Copy link
Contributor

Currently k4run automatically attaches and runs gdb on a crash to get a backtrace. To arrive at an actual backtrace a significant amount of time passes. I think this should not be the default.
@tmadlener tmadlener added the enhancement New feature or request label Nov 28, 2022
This was referenced Jan 7, 2023
Merged
Merged
@tmadlener
Copy link
Contributor Author

I was wrong with attributing the fault to k4run. It is actually root that attaches the debugger on a crash. Hence, to cut out the debugger it is necessary to change the Root.Stacktrace setting to no in an appropriate .rootrc file, as the default one that is shipped with root in $ROOTSYS/etc/system.rootrc contains

Root.Stacktrace:    yes

A ~/.rootrc with

Root.Stacktrace: no

will disable the stacktrace "globally", however, a ./.rootrc in the folder where k4run is executed with the same contents offers a more granular disabling of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tmadlener