https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #21 from jody <jody....@gmail.com> --- oops - this did not work. Which mail address should i use to share the link with? On Thu, Jan 2, 2020 at 11:59 AM jody <jody....@gmail.com> wrote: > I did > objdump -d /usr/lib64/libhdf5.so.103.1.0 > > objdump_libhdf5.so.103.1.0.txt > but the string "H5P_dup_prop" is not in the output. > The command 'grep "H5P_d" objdump_libhdf5.so.103.1.0.txt' returns nothing. > The next function in the stack (H5P__do_prop_cb1) does also not occur in > the output of objdump, but all others are. > > I sent a dropbox link for objdump_libhdf5.so.103.1.0.txt to > bug-cont...@kde.org > > > On Thu, Jan 2, 2020 at 12:28 PM Julian Seward <bugzilla_nore...@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=393351 >> >> --- Comment #18 from Julian Seward <jsew...@acm.org> --- >> As Tom says .. >> >> > ==6297== valgrind: Unrecognised instruction at address 0x4a54820. >> > ==6297== at 0x4A54820: H5P_dup_prop+64 (in >> /usr/lib64/libhdf5.so.103.1.0) >> >> > I have no experience at all with objdump. I tried 'objdump -d >> ./h5s_8.3.0' >> >> Nearly, not quite right. The problem is in /usr/lib64/libhdf5.so.103.1.0. >> >> Can you try objdump -d /usr/lib64/libhdf5.so.103.1.0 instead? >> >> Then look for the code near the entry point (to be precise, at offset 64 >> from) >> for H5P_dup_prop. You can find that entry point by searching the objdump >> output for the string >> >> H5P_dup_prop>: >> >> -- >> You are receiving this mail because: >> You are on the CC list for the bug. > > -- You are receiving this mail because: You are watching all bug changes.
