perf: unwind: pass symbol source to libunwind
PATCH v2 1/3 perf: unwind: pass symbol source to libunwind
Even if --symfs is used to point to the debug binaries, we send in the non-debug filenames to libunwind, which leads to libunwind not finding the debug frame. Fix this by preferring the file in --symfs, if it is available.
---
v2: fall back to ->name if ->symsrc_filename is NULL
tools/perf/util/unwind-libunwind.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
tools/perf/util/unwind-libunwind.c +4 -1
@@ -360,12 +360,15 @@ find_proc_info(unw_addr_space_t as, unw_word_t ip, unw_proc_info_t *pi,int fd =dso__data_get_fd (map->dso, ui->machine);int is_exec =elf_is_exec (fd, map->dso->name);unw_word_t base = is_exec ?0 : map->start; +const char *symfile;if (fd >=0 )dso__data_put_fd (map->dso); + symfile = map->dso->symsrc_filename ?: map->dso->name; +memset (&di,0 ,sizeof (di)); -if (dwarf_find_debug_frame (0 , &di, ip, base, map->dso->name, +if (dwarf_find_debug_frame (0 , &di, ip, base, symfile, map->start, map->end))return dwarf_search_unwind_table (as, ip, &di, pi, need_unwind_info, arg);
Signature · 1 line
1.7.10.4
PATCH v2 2/3 tools: build: fix libiberty feature detection
Any CFLAGS or LDFLAGS set by the user need to be passed to the feature build command. This many include for example -I or -L to point to libraries and include files in custom paths.
In most of the test-*.bin rules in build/feature/Makefile, we use the BUILD macro which always sends in CFLAGS and LDFLAGS. The libiberty build line however doesn't use the BUILD macro and thus needs to send in CFLAGS and LDFLAGS explicitly. Without this, when using custom CFLAGS/LDFLAGS, libiberty fails to be detected and the perf link fails with something like:
LINK perf
libbfd.a(bfd.o): In function `bfd_errmsg':
bfd.c:(.text+0x168): undefined reference to xstrerror' bbfd.a(opncls.o): In function _bfd_new_bfd':
opncls.c:(.text+0xe8): undefined reference to `objalloc_create'
...
---
v2: rewrite commit message
tools/build/feature/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
tools/build/feature/Makefile +2 -2
@@ -132,10 +132,10 @@ test-libbfd.bin: $(BUILD) -DPACKAGE='"perf"' -lbfd -lz -liberty -ldl test-liberty.bin: - $(CC) -Wall -Werror -o $(OUTPUT)$@ test-libbfd.c -DPACKAGE='"perf"' -lbfd -ldl -liberty + $(CC) $(CFLAGS) -Wall -Werror -o $(OUTPUT)$@ test-libbfd.c -DPACKAGE='"perf"' $(LDFLAGS) -lbfd -ldl -liberty test-liberty-z.bin: - $(CC) -Wall -Werror -o $(OUTPUT)$@ test-libbfd.c -DPACKAGE='"perf"' -lbfd -ldl -liberty -lz + $(CC) $(CFLAGS) -Wall -Werror -o $(OUTPUT)$@ test-libbfd.c -DPACKAGE='"perf"' $(LDFLAGS) -lbfd -ldl -liberty -lz test-cplus-demangle.bin: $(BUILD) -liberty
Signature · 1 line
1.7.10.4
Re: [PATCHv2 2/3] tools: build: fix libiberty feature detection
Quoted 10 lines · Rabin Vincent
Any CFLAGS or LDFLAGS set by the user need to be passed to the feature build command. This many include for example -I or -L to point to libraries and include files in custom paths.
In most of the test-*.bin rules in build/feature/Makefile, we use the BUILD macro which always sends in CFLAGS and LDFLAGS. The libiberty build line however doesn't use the BUILD macro and thus needs to send in CFLAGS and LDFLAGS explicitly. Without this, when using custom CFLAGS/LDFLAGS, libiberty fails to be detected and the perf link fails with something like:
Quoted 8 lines
LINK perf
libbfd.a(bfd.o): In function `bfd_errmsg':
bfd.c:(.text+0x168): undefined reference toxstrerror' bbfd.a(opncls.o): In function_bfd_new_bfd':
opncls.c:(.text+0xe8): undefined reference to `objalloc_create'
...Signed-off-by Rabin Vincent <[email protected]>
thanks,
jirka
tip-bot for Rabin Vincent
merge bot[tip:perf/core] tools build: Fix libiberty feature detection
In reply to Rabin Vincenttools build: Fix libiberty feature detection
Commit-ID: 3af6ed84eb43c587beb5f3252222e39e65d08c61 Gitweb: http://git.kernel.org/tip/3af6ed84eb43c587beb5f3252222e39e65d08c61 Author: Rabin Vincent <[email protected]> AuthorDate: Thu, 29 Oct 2015 08:49:37 +0100 Committer: Arnaldo Carvalho de Melo <[email protected]> CommitDate: Thu, 29 Oct 2015 17:46:35 -0300
tools build: Fix libiberty feature detection
Any CFLAGS or LDFLAGS set by the user need to be passed to the feature build command. This many include for example -I or -L to point to libraries and include files in custom paths.
In most of the test-*.bin rules in build/feature/Makefile, we use the BUILD macro which always sends in CFLAGS and LDFLAGS. The libiberty build line however doesn't use the BUILD macro and thus needs to send in CFLAGS and LDFLAGS explicitly. Without this, when using custom CFLAGS/LDFLAGS, libiberty fails to be detected and the perf link fails with something like:
LINK perf
libbfd.a(bfd.o): In function `bfd_errmsg':
bfd.c:(.text+0x168): undefined reference to xstrerror' bbfd.a(opncls.o): In function _bfd_new_bfd':
opncls.c:(.text+0xe8): undefined reference to `objalloc_create'
...
--- tools/build/feature/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
tools/build/feature/Makefile +2 -2
@@ -132,10 +132,10 @@ test-libbfd.bin: $(BUILD) -DPACKAGE='"perf"' -lbfd -lz -liberty -ldl test-liberty.bin: - $(CC) -Wall -Werror -o $(OUTPUT)$@ test-libbfd.c -DPACKAGE='"perf"' -lbfd -ldl -liberty + $(CC) $(CFLAGS) -Wall -Werror -o $(OUTPUT)$@ test-libbfd.c -DPACKAGE='"perf"' $(LDFLAGS) -lbfd -ldl -liberty test-liberty-z.bin: - $(CC) -Wall -Werror -o $(OUTPUT)$@ test-libbfd.c -DPACKAGE='"perf"' -lbfd -ldl -liberty -lz + $(CC) $(CFLAGS) -Wall -Werror -o $(OUTPUT)$@ test-libbfd.c -DPACKAGE='"perf"' $(LDFLAGS) -lbfd -ldl -liberty -lz test-cplus-demangle.bin: $(BUILD) -liberty
PATCH v2 3/3 perf: add helper makefile for cross compiling libs
In reply to Rabin VincentIt's easy to cross-compile a minimal perf binary without any external libraries (other than a C library of course). But many useful features depend on external libraries, so to get them one needs to either cross-compile a bunch of libraries manually and send in the correct paths or integrate the perf build into some external build system.
In order to make it easier for people to qucikly get up and running with a fairly full featured cross-compiled mainline perf, provide a helper makefile which can be used to download and build the required libraries, which can then be used in a static build of perf.
For example, assuming an arm-linux-gcc cross-compiler is present in the PATH, the following is what one seens if one tries to build a static perf for ARM:
$ make ARCH=arm CROSS_COMPILE=arm-linux- LDFLAGS="-static"
Auto-detecting system features:
... dwarf: [ OFF ]
... glibc: [ on ]
... gtk2: [ OFF ]
... libaudit: [ OFF ]
... libbfd: [ OFF ]
... libelf: [ OFF ]
... libnuma: [ OFF ]
... numa_num_possible_cpus: [ OFF ]
... libperl: [ OFF ]
... libpython: [ OFF ]
... libslang: [ OFF ]
... libunwind: [ OFF ]
... libdw-dwarf-unwind: [ OFF ]
... zlib: [ OFF ]
... lzma: [ OFF ]
... get_cpuid: [ OFF ]
By using the new Makefile.cross first, we get many important features:
$ make ARCH=arm CROSS_COMPILE=arm-linux- -f Makefile.cross $ make ARCH=arm CROSS_COMPILE=arm-linux- LDFLAGS="-static"
Auto-detecting system features:
... dwarf: [ on ] ... glibc: [ on ] ... gtk2: [ OFF ] ... libaudit: [ on ] ... libbfd: [ on ] ... libelf: [ on ] ... libnuma: [ OFF ] ... numa_num_possible_cpus: [ OFF ] ... libperl: [ OFF ] ... libpython: [ OFF ] ... libslang: [ on ] ... libunwind: [ on ] ... libdw-dwarf-unwind: [ OFF ] ... zlib: [ on ] ... lzma: [ on ]
... get_cpuid: [ OFF ]
---
v2: expand commit message, add comments in Makefile, rename to Makefile.cross
tools/perf/Makefile.cross | 154 +++++++++++++++++++++++++++++++++++++++++++++ tools/perf/Makefile.perf | 7 +++ 2 files changed, 161 insertions(+) create mode 100644 tools/perf/Makefile.cross
tools/perf/Makefile.cross new file +154 -0
@@ -0,0 +1,154 @@ +# +# This is a helper Makefile that downloads and builds many of the optional +# libraries that perf can use. This libraries built by this Makefile can be +# subsequently used in a static build of perf. The intented use is when cross +# compiling perf. +# +# For example, assuming you have the arm-linux-gcc cross compiler in your PATH, +# running the following two commands will result in a static ARM build of perf +# with various features that require external libraries: +# +# $ make ARCH=arm CROSS_COMPILE=arm-linux- -f Makefile.cross +# $ make ARCH=arm CROSS_COMPILE=arm-linux- LDFLAGS="-static" +# + +LIBS += audit +audit_BASENAME=audit-2.4.4 +audit_ARCHIVE=$(audit_BASENAME).tar.gz +audit_URL=https://people.redhat.com/sgrubb/audit/$(audit_ARCHIVE) + +LIBS += bfd +bfd_BASENAME=binutils-2.25.1 +bfd_ARCHIVE=$(bfd_BASENAME).tar.bz2 +bfd_URL=http://ftp.gnu.org/gnu/binutils/$(bfd_ARCHIVE) + +LIBS += bzip2 +bzip2_BASENAME=bzip2-1.0.6 +bzip2_ARCHIVE=$(bzip2_BASENAME).tar.gz +bzip2_URL=http://www.bzip.org/1.0.6/$(bzip2_ARCHIVE) + +LIBS += elfutils +elfutils_BASENAME=elfutils-0.163 +elfutils_ARCHIVE=$(elfutils_BASENAME).tar.bz2 +elfutils_URL=https://fedorahosted.org/releases/e/l/elfutils/0.163/$(elfutils_ARCHIVE) + +LIBS += lzma +lzma_BASENAME=xz-5.2.1 +lzma_ARCHIVE=$(lzma_BASENAME).tar.gz +lzma_URL=http://tukaani.org/xz/$(lzma_ARCHIVE) + +LIBS += slang +slang_BASENAME=slang-2.1.4 +slang_ARCHIVE=$(slang_BASENAME).tar.bz2 +slang_URL=http://ftp.ntua.gr/pub/lang/slang/slang/v2.1/$(slang_ARCHIVE) + +LIBS += unwind +unwind_BASENAME=libunwind-1.1 +unwind_ARCHIVE=$(unwind_BASENAME).tar.gz +unwind_URL=http://download.savannah.gnu.org/releases/libunwind/$(unwind_ARCHIVE) + +LIBS += zlib +zlib_BASENAME=zlib-1.2.8 +zlib_ARCHIVE=$(zlib_BASENAME).tar.gz +zlib_URL=http://zlib.net/$(zlib_ARCHIVE) + +DLDIR=dl +DEPSDIR=deps-$(ARCH) +BUILDDIR=build-$(ARCH) +HOST=$(shell echo $(CROSS_COMPILE) | sed 's/.$$//') +PREFIX=$(realpath $(shell pwd))/$(DEPSDIR) +MAKE1=$(MAKE) -j1 + +CC=$(CROSS_COMPILE)gcc + +export CC + +.PHONY: all clean $(LIBS) + +all: $(LIBS) + +define LIB_template +$1_DIR=$$(BUILDDIR)/$$($1_BASENAME) +$1_EXTRACT=$$($1_DIR)/.extract +$1_INSTALL=$$(DEPSDIR)/lib/.$1.install + +$$(DLDIR)/$$($1_ARCHIVE): + mkdir -p $$(DLDIR) && cd $$(DLDIR) && wget -N $$($1_URL) + +$$($1_EXTRACT): $$(DLDIR)/$$($1_ARCHIVE) + mkdir -p $$(BUILDDIR) && tar xf $$< -C $$(BUILDDIR) + touch $$@ + +$1: $$($1_INSTALL) + +$1-clean: + rm -rf $$($1_DIR) +endef + +$(foreach lib,$(LIBS),$(eval $(call LIB_template,$(lib)))) + +$(audit_INSTALL): $(audit_EXTRACT) + cd $(audit_DIR) && ./configure --host=$(HOST) --prefix=$(PREFIX) + $(MAKE) -C $(audit_DIR)/lib + $(MAKE) -C $(audit_DIR)/lib install + touch $@ + +CFLAGS=-I$(PREFIX)/include +LDFLAGS=-L$(PREFIX)/lib + +$(bfd_INSTALL): $(zlib_INSTALL) $(bfd_EXTRACT) + cd $(bfd_DIR)/libiberty && ./configure --host=$(HOST) --prefix=$(PREFIX) --enable-install-libiberty + $(MAKE) -C $(bfd_DIR)/libiberty + $(MAKE) -C $(bfd_DIR)/libiberty install + cd $(bfd_DIR)/bfd && CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS)" ./configure --host=$(HOST) --prefix=$(PREFIX) --with-zlib + $(MAKE) -C $(bfd_DIR)/bfd + $(MAKE) -C $(bfd_DIR)/bfd install + touch $@ + +$(bzip2_INSTALL): $(bzip2_EXTRACT) + $(MAKE) -C $(bzip2_DIR) clean + $(MAKE) CC="$(CC)" PREFIX=$(PREFIX) -C $(bzip2_DIR) -f Makefile-libbz2_so + mkdir -p $(DEPSDIR)/lib + cp -a $(bzip2_DIR)/libbz2.so* $(DEPSDIR)/lib/ + @rm -f $(DEPSDIR)/lib/libbz2.so + # The dynamic library is required to prevent errors while building elfutils + cd $(DEPSDIR)/lib && ln -s libbz2.so.1.0 libbz2.so + $(MAKE) -C $(bzip2_DIR) clean + $(MAKE) CC="$(CC)" PREFIX=$(PREFIX) -C $(bzip2_DIR) install + touch $@ + +elfutils_LDFLAGS=$(LDFLAGS) -Wl,-rpath-link $(PREFIX)/lib + +$(elfutils_INSTALL): $(zlib_INSTALL) $(lzma_INSTALL) $(bzip2_INSTALL) $(elfutils_EXTRACT) + cd $(elfutils_DIR) && CFLAGS="$(CFLAGS)" LDFLAGS="$(elfutils_LDFLAGS)" ./configure --host=$(HOST) --prefix=$(PREFIX) --with-zlib --with-bzlib --with-lzma + $(MAKE) -C $(elfutils_DIR) + $(MAKE) -C $(elfutils_DIR) install + touch $@ + +$(lzma_INSTALL): $(lzma_EXTRACT) + cd $(lzma_DIR) && ./configure --host=$(HOST) --prefix=$(PREFIX) + $(MAKE) -C $(lzma_DIR) + $(MAKE) -C $(lzma_DIR) install + touch $@ + +$(slang_INSTALL): $(slang_EXTRACT) + cd $(slang_DIR) && ./configure --host=$(HOST) --prefix=$(PREFIX) + $(MAKE1) -C $(slang_DIR) + $(MAKE1) -C $(slang_DIR) install-all + touch $@ + +$(zlib_INSTALL): $(zlib_EXTRACT) + cd $(zlib_DIR) && ./configure --prefix=$(PREFIX) + $(MAKE) -C $(zlib_DIR) + $(MAKE) -C $(zlib_DIR) install + touch $@ + +$(unwind_INSTALL): $(unwind_EXTRACT) + cd $(unwind_DIR) && ./configure --host=$(HOST) --prefix=$(PREFIX) --enable-debug --enable-debug-frame + cd $(unwind_DIR) && $(MAKE) + cd $(unwind_DIR) && $(MAKE) install + touch $@ + +clean: + rm -rf $(BUILDDIR) + rm -rf $(DEPSDIR)
tools/perf/Makefile.perf +7 -0
@@ -92,6 +92,13 @@ ifneq ($(objtree),) #$(info Determined 'objtree' to be $(objtree)) endif +ifeq ($(findstring -static,${LDFLAGS}),-static) + ifneq ($(wildcard deps-$(ARCH)/*),) + LDFLAGS += -L $(PWD)/deps-$(ARCH)/lib + EXTRA_CFLAGS += -isystem $(PWD)/deps-$(ARCH)/include + endif +endif + ifneq ($(OUTPUT),) #$(info Determined 'OUTPUT' to be $(OUTPUT)) # Adding $(OUTPUT) as a directory to look for source files,
Signature · 1 line
1.7.10.4
Re: [PATCHv2 3/3] perf: add helper makefile for cross compiling libs
Quoted 56 lines · Rabin Vincent
It's easy to cross-compile a minimal perf binary without any external libraries (other than a C library of course). But many useful features depend on external libraries, so to get them one needs to either cross-compile a bunch of libraries manually and send in the correct paths or integrate the perf build into some external build system.
In order to make it easier for people to qucikly get up and running with a fairly full featured cross-compiled mainline perf, provide a helper makefile which can be used to download and build the required libraries, which can then be used in a static build of perf.
For example, assuming an arm-linux-gcc cross-compiler is present in the PATH, the following is what one seens if one tries to build a static perf for ARM:
$ make ARCH=arm CROSS_COMPILE=arm-linux- LDFLAGS="-static"Auto-detecting system features:
... dwarf: [ OFF ]
... glibc: [ on ]
... gtk2: [ OFF ]
... libaudit: [ OFF ]
... libbfd: [ OFF ]
... libelf: [ OFF ]
... libnuma: [ OFF ]
...numa_num_possible_cpus: [ OFF ]
... libperl: [ OFF ]
... libpython: [ OFF ]
... libslang: [ OFF ]
... libunwind: [ OFF ]
... libdw-dwarf-unwind: [ OFF ]
... zlib: [ OFF ]
... lzma: [ OFF ]
...get_cpuid: [ OFF ]By using the new Makefile.cross first, we get many important features:
$ make ARCH=arm CROSS_COMPILE=arm-linux- -f Makefile.cross $ make ARCH=arm CROSS_COMPILE=arm-linux- LDFLAGS="-static"Auto-detecting system features:
... dwarf: [ on ] ... glibc: [ on ] ... gtk2: [ OFF ] ... libaudit: [ on ] ... libbfd: [ on ] ... libelf: [ on ] ... libnuma: [ OFF ] ... numa_num_possible_cpus: [ OFF ] ... libperl: [ OFF ] ... libpython: [ OFF ] ... libslang: [ on ] ... libunwind: [ on ] ... libdw-dwarf-unwind: [ OFF ] ... zlib: [ on ] ... lzma: [ on ]
Quoted 1 line
...
get_cpuid: [ OFF ]
That's really nice!
Would it be possible to add a gcc and glibc building portion as well? That would make it entirely self-hosting.
Something like:
make ARCH=arm BOOTSTRAP=1
... would magically fetch everything needed, and (given enough Internet bandwidth and a fast enough machine) build a whole cross-environment from scratch.
Personally I'd even use this to bootstrap kernel cross-builds.
It could also be used to cross-build to the host architecture as well: it would make it easier to test perf on the latest GCC and glibc versions. (Which the host distribution does not carry.)
Thanks,
Ingo
Re: [PATCHv2 3/3] perf: add helper makefile for cross compiling libs
Quoted 2 lines · Ingo Molnar
Would it be possible to add a gcc and glibc building portion as well? That would make it entirely self-hosting.
Yes, but:
- Those that intend to run the built binary on a target would presumably already have a cross-compiler lying around which they use to build the rest of userspace.
- Those that don't have a cross-compiler or need a newer one can already very easily create one using other specialized tools such as crosstool-ng (see below).
Quoted 7 lines
Something like:
make ARCH=arm BOOTSTRAP=1
... would magically fetch everything needed, and (given enough Internet bandwidth and a fast enough machine) build a whole cross-environment from scratch.
This is already possible using crosstool-ng. Getting an ARM GCC 5.2 cross-compiler is as simple as:
$ git clone git://crosstool-ng.org/crosstool-ng $ cd crosstool-ng $ ./bootstrap && ./configure --enable-local && make
$ ./ct-ng arm-unknown-linux-gnueabi $ ./ct-ng build
$ export PATH=$PATH:~/x-tools/arm-unknown-linux-gnueabi/bin/ $ arm-unknown-linux-gnueabi-gcc --version arm-unknown-linux-gnueabi-gcc (crosstool-NG crosstool-ng-1.20.0-361-g85f9814) 5.2.0
Quoted 5 lines
Personally I'd even use this to bootstrap kernel cross-builds.
It could also be used to cross-build to the host architecture as well: it would make it easier to test perf on the latest GCC and glibc versions. (Which the host distribution does not carry.)
This is also possible with crosstool-ng. You just need to build the x86_64-unknown-linux-gnu config to get GCC 5.2 + glibc 2.22 toolchain for an x86-64 host.
Re: [PATCHv2 3/3] perf: add helper makefile for cross compiling libs
Quoted 28 lines · Rabin Vincent
Quoted 2 lines · Ingo Molnar
Would it be possible to add a gcc and glibc building portion as well? That would make it entirely self-hosting.
Yes, but:
- Those that intend to run the built binary on a target would presumably already have a cross-compiler lying around which they use to build the rest of userspace.
- Those that don't have a cross-compiler or need a newer one can already very easily create one using other specialized tools such as crosstool-ng (see below).
Quoted 7 lines
Something like:
make ARCH=arm BOOTSTRAP=1
... would magically fetch everything needed, and (given enough Internet bandwidth and a fast enough machine) build a whole cross-environment from scratch.
This is already possible using crosstool-ng. Getting an ARM GCC 5.2 cross-compiler is as simple as:
Quoted 6 lines
$ git clone git://crosstool-ng.org/crosstool-ng $ cd crosstool-ng $ ./bootstrap && ./configure --enable-local && make$ ./ct-ng arm-unknown-linux-gnueabi $ ./ct-ng build
My point is, that's 5 non-trivial steps harder than just typing:
make ARCH=arm BOOTSTRAP=1
Quoted 3 lines
This is also possible with crosstool-ng. You just need to build the x86_64-unknown-linux-gnu config to get GCC 5.2 + glibc 2.22 toolchain for an x86-64 host.
It's also possibly by directly cloning the repos of those tools and building them
- they are reasonably easy to build.
My point is that if we add automation, we might as well walk to whole mile.
Thanks,
Ingo
tip-bot for Rabin Vincent
merge bot[tip:perf/core] perf unwind: Pass symbol source to libunwind
In reply to Rabin Vincentperf unwind: Pass symbol source to libunwind
Commit-ID: 7ed4915ad60788d6b846e2cd034f49ee15698143 Gitweb: http://git.kernel.org/tip/7ed4915ad60788d6b846e2cd034f49ee15698143 Author: Rabin Vincent <[email protected]> AuthorDate: Thu, 29 Oct 2015 08:49:36 +0100 Committer: Arnaldo Carvalho de Melo <[email protected]> CommitDate: Thu, 29 Oct 2015 17:48:38 -0300
perf unwind: Pass symbol source to libunwind
Even if --symfs is used to point to the debug binaries, we send in the non-debug filenames to libunwind, which leads to libunwind not finding the debug frame. Fix this by preferring the file in --symfs, if it is available.
--- tools/perf/util/unwind-libunwind.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
tools/perf/util/unwind-libunwind.c +4 -1
@@ -360,12 +360,15 @@ find_proc_info(unw_addr_space_t as, unw_word_t ip, unw_proc_info_t *pi,int fd =dso__data_get_fd (map->dso, ui->machine);int is_exec =elf_is_exec (fd, map->dso->name);unw_word_t base = is_exec ?0 : map->start; +const char *symfile;if (fd >=0 )dso__data_put_fd (map->dso); + symfile = map->dso->symsrc_filename ?: map->dso->name; +memset (&di,0 ,sizeof (di)); -if (dwarf_find_debug_frame (0 , &di, ip, base, map->dso->name, +if (dwarf_find_debug_frame (0 , &di, ip, base, symfile, map->start, map->end))return dwarf_search_unwind_table (as, ip, &di, pi, need_unwind_info, arg);