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

Use the correct macro to include backtrace #4453

Closed
wants to merge 1 commit into from
Closed

Use the correct macro to include backtrace #4453

wants to merge 1 commit into from

Conversation

clandmeter
Copy link
Contributor

execinfo.h and backtrace() are GNU extensions provided by glibc and not by gcc
http://www.gnu.org/software/libc/manual/html_mono/libc.html#Backtraces

Splitted from #4385

execinfo.h and backtrace() are GNU extensions provided by glibc and not by gcc
http://www.gnu.org/software/libc/manual/html_mono/libc.html#Backtraces
@ironMann
Copy link
Contributor

More universal attempt at obtaining stack trace would be to attach a debugger to self, print usable information and return. Similar to zloop.sh:96-98

@behlendorf
Copy link
Contributor

@ironMann yes, in fact we could no revert the original patch which added this backtrace support since we are now using zloop.sh in the test infrastructure.

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.

3 participants