-rdynamic seems to create general symbols in .dynsym #10
Comments
honggyukim
added a commit
that referenced
this issue
Jul 11, 2021
Sometimes it's useful to print backtrace or stacktrace by explicitly
write a request inside source code.
This patch implements stacktrace() function for this. It's implemented
in two different versions. In debug mode, it uses an external libunwind
library and it's output looks as follows.
Stack trace:
#1 0x000000449ef9 parse_argspec + 0x5d6
#2 0x00000044b76c parse_argument_spec + 0x70
#3 0x00000044bf58 setup_trigger_action + 0x146
#4 0x0000004329e5 find_dwarf_argspec + 0x153
#5 0x000000432b18 find_auto_argspec + 0x4c
#6 0x00000044b102 add_filter + 0x87
#7 0x00000044c1bf add_trigger_entry + 0x15c
#8 0x00000044c61f setup_trigger + 0x413
#9 0x00000044c85b uftrace_setup_argument + 0x59
#10 0x00000044e053 build_arg_spec + 0x4f
#11 0x00000042a6fe walk_sessions + 0x4a
#12 0x00000044e12d setup_fstack_args + 0x7d
#13 0x00000043a353 open_data_file + 0x3ff
#14 0x0000004171a5 command_replay + 0x7a
#15 0x000000407ba9 main + 0x4c3
#16 0x7f4e1df33840 __libc_start_main + 0xf0
#17 0x000000405499 _start + 0x29
In release mode, it's better not to rely on an external library, so it
just uses builtin backtrace() function, but it can't print static
functions. The example output looks as follows.
Stack trace:
#1 uftrace(parse_argspec+0x4d1) [0x43dd01]
#2 uftrace() [0x43e44c]
#3 uftrace(setup_trigger_action+0xb0) [0x43f4e0]
#4 uftrace() [0x42a933]
#5 uftrace(find_auto_argspec+0x29) [0x42aff9]
#6 uftrace() [0x43f2f7]
#7 uftrace() [0x43fa20]
#8 uftrace() [0x440140]
#9 uftrace(walk_sessions+0x39) [0x4248a9]
#10 uftrace(setup_fstack_args+0xa6) [0x440bb6]
#11 uftrace(open_data_file+0x16f) [0x43012f]
#12 uftrace(command_replay+0x59) [0x415ee9]
#13 uftrace(main+0x544) [0x40adc4]
#14 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f8e3d944840]
#15 uftrace(_start+0x29) [0x40aef9]
Signed-off-by: Honggyu Kim <[email protected]>
honggyukim
added a commit
that referenced
this issue
Jul 11, 2021
Sometimes it's useful to print backtrace or stacktrace by explicitly
write a request inside source code.
This patch implements stacktrace() function for this. It's implemented
in two different versions. In debug mode, it uses an external libunwind
library and it's output looks as follows.
Stack trace:
#1 0x000000449ef9 parse_argspec + 0x5d6
#2 0x00000044b76c parse_argument_spec + 0x70
#3 0x00000044bf58 setup_trigger_action + 0x146
#4 0x0000004329e5 find_dwarf_argspec + 0x153
#5 0x000000432b18 find_auto_argspec + 0x4c
#6 0x00000044b102 add_filter + 0x87
#7 0x00000044c1bf add_trigger_entry + 0x15c
#8 0x00000044c61f setup_trigger + 0x413
#9 0x00000044c85b uftrace_setup_argument + 0x59
#10 0x00000044e053 build_arg_spec + 0x4f
#11 0x00000042a6fe walk_sessions + 0x4a
#12 0x00000044e12d setup_fstack_args + 0x7d
#13 0x00000043a353 open_data_file + 0x3ff
#14 0x0000004171a5 command_replay + 0x7a
#15 0x000000407ba9 main + 0x4c3
#16 0x7f4e1df33840 __libc_start_main + 0xf0
#17 0x000000405499 _start + 0x29
In release mode, it's better not to rely on an external library, so it
just uses builtin backtrace() function, but it can't print static
functions. The example output looks as follows.
Stack trace:
#1 uftrace(parse_argspec+0x4d1) [0x43dd01]
#2 uftrace() [0x43e44c]
#3 uftrace(setup_trigger_action+0xb0) [0x43f4e0]
#4 uftrace() [0x42a933]
#5 uftrace(find_auto_argspec+0x29) [0x42aff9]
#6 uftrace() [0x43f2f7]
#7 uftrace() [0x43fa20]
#8 uftrace() [0x440140]
#9 uftrace(walk_sessions+0x39) [0x4248a9]
#10 uftrace(setup_fstack_args+0xa6) [0x440bb6]
#11 uftrace(open_data_file+0x16f) [0x43012f]
#12 uftrace(command_replay+0x59) [0x415ee9]
#13 uftrace(main+0x544) [0x40adc4]
#14 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f8e3d944840]
#15 uftrace(_start+0x29) [0x40aef9]
Signed-off-by: Honggyu Kim <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Inside ELF Symbol Tables (.symtab and .dynsym)
The text was updated successfully, but these errors were encountered: