mismatch with glibc backtrace about libbacktrace

[ianlancetaylor]

When using backtrace_full from libbacktrace you get the debugging info. In your case there is no debugging info for the startup code. You can get information similar to glibc backtrace by calling the libbacktrace function backtrace_syminfo.

[nagarajsherigar]

When using backtrace_full from libbacktrace you get the debugging info. In your case there is no debugging info for the startup code. You can get information similar to glibc backtrace by calling the libbacktrace function backtrace_syminfo.

yes.i can use that function.still it will not show from which module it is picking,like ex /lib/x86_64-linux-gnu/libc.so.6

also couple more queries

1. is it safe to use backtrace_full in SIGSEGV signal handler ?
2. In backtrace_syminfo_callback what does symval and symsize mean?

[ianlancetaylor]

It is safe to use backtrace_full in a signal handler.

In the backtrace_syminfo_callback function symval is the address of the symbol in memory. symsize is the size of the symbol as recorded in the executable's symbol table. This is normally the size of the function or the variable.

[nagarajsherigar]

It is safe to use backtrace_full in a signal handler.

In the backtrace_syminfo_callback function symval is the address of the symbol in memory. symsize is the size of the symbol as recorded in the executable's symbol table. This is normally the size of the function or the variable.

backtrace_full uses mmap.mmap is not in async safe list of functions,so just wanted to understand,how it is safe?

[ianlancetaylor]

mmap is async-signal-safe in practice.