You may want to try to apply this patch - https://groups.google.com/forum/#!topic/osv-dev/LbnnY2Kcmak - that should provide many useful debug printouts.
There is another patch I have sent that fixes the versioned self-lookup problem - https://groups.google.com/forum/#!topic/osv-dev/d56plMGXi6E. I wonder if it fixes your problem (my gut tells me yours is different). On Tuesday, December 10, 2019 at 3:07:09 AM UTC-5, Nadav Har'El wrote: > > On Mon, Dec 9, 2019 at 10:51 PM zhiting zhu <zzt...@gmail.com > <javascript:>> wrote: > >> Hey, >> >> I'm encountering this when I'm using some tensorflow functions: >> >> /lib/python3.6/tensorflow/python/_pywrap_tensorflow_internal.so: failed >> looking up symbol >> > > This is interesting, because the "failed looking up symbol" message is > always followed by the name of the symbol looked up: > > core/elf.cc: abort("%s: failed looking up symbol %s\n", > pathname().c_str(), demangle(name).c_str()); > > You can try to add printouts in object::arch_relocate_rela() to try to > understand which symbol() is being called > with an empty name. > > >> [backtrace] >> 0x00000000403442a7 <elf::object::symbol(unsigned int, bool)+391> >> 0x0000000040397dce <elf::object::arch_relocate_rela(unsigned int, >> unsigned int, void*, long)+574> >> > > >> 0x000000004033eed4 <elf::object::relocate_rela()+196> >> 0x0000000040341d27 <elf::object::relocate()+199> >> 0x0000000040345623 >> <elf::program::load_object(std::__cxx11::basic_string<char, >> std::char_traits<char>, std::allocator<char> >, >> std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, >> std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, >> std::char_traits<char>, std::allocator<char> > > >, >> std::vector<std::shared_ptr<elf::object>, >> std::allocator<std::shared_ptr<elf::object> > >&)+1459> >> 0x0000000040345e70 >> <elf::program::get_library(std::__cxx11::basic_string<char, >> std::char_traits<char>, std::allocator<char> >, >> std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, >> std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, >> std::char_traits<char>, std::allocator<char> > > >, bool)+336> >> 0x0000000040465fd8 <dlopen+136> >> 0x0000100000937228 <_PyImport_FindSharedFuncptr+376> >> 0x745f70617277796f <???+1920432495> >> >> It seems the name is not print out. >> >> If I'm using the check-libcfunc-avail.sh to check the >> _pywrap_tensorflow_internal.so, I get the following output: >> >> pthread_mutex_consistent not found >> pthread_mutexattr_setrobust not found >> fmaf not found >> fma not found >> mallinfo not found >> > > All of these we should eventually add, these are real Linux glibc > functions... > Feel free to open issues about them, or propose patches - some will be > trivial (e.g., fma() is already defined in musl/ we just need to enable it > in the Makefile). > > 0000000000000000 not found >> DF not found >> *UND* not found >> 0000000000000000 not found >> (GLIBC_2.2.5) not found >> > > These may be (hopefully) parsing errors by the script? > > >> mremap not found >> > > Eventually will need to do this too... > https://github.com/cloudius-systems/osv/issues/184 > >> >> Originally, it also contains some output of missing complex number >> related functions. I include those from musl. The list reduces to the >> above. >> >> It would be great to know which symbol it's missing. I'm not sure whether >> it's looking for a symbol from libc or from other library. >> >> Best, >> Zhiting >> >> -- >> You received this message because you are subscribed to the Google Groups >> "OSv Development" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to osv...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/osv-dev/d84f4991-69d5-45d8-98a2-403257c9e4b2%40googlegroups.com >> >> <https://groups.google.com/d/msgid/osv-dev/d84f4991-69d5-45d8-98a2-403257c9e4b2%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to osv-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osv-dev/4a72dd0b-b20a-4877-94da-aa9313add35e%40googlegroups.com.
