Hi all, My first message didn''t seem to go through so I am giving it another try. Sorry for the spam. I am working on a Xen related project and I hit an assertion in the Xen''s code. I obtained the memory image using kdump and was about to extract the hypervisor stack trace from it. However, I had trouble getting the python script dom0cut.py to work. I followed the instruction on Xen wiki to install libelf.0.8.9 [1] and the libelf wrapper [2]. I had to manually create a softlink "/usr/lib/libelf.so.1" to point to libelf-0.8.9.so or the script would complain. Also, the script seemed to require eu-readelf to work. Therefore, I had to install elfutils (0.123-3). Then, I ran into the following errors: Traceback (most recent call last): File "/usr/bin/dom0cut.py", line 8, in ? import xendump.XenCore File "/usr/lib/python2.4/site-packages/xendump/XenCore.py", line 7, in ? import xendump.CoreDump as CoreDump File "/usr/lib/python2.4/site-packages/xendump/CoreDump.py", line 1, in ? import xendump.Arch as Arch File "/usr/lib/python2.4/site-packages/xendump/Arch.py", line 1, in ? import libelf File "/usr/lib/python2.4/site-packages/libelf/__init__.py", line 10, in ? from libelf import * File "/usr/lib/python2.4/site-packages/libelf/libelf.py", line 5, in ? import _libelf ImportError: /usr/lib/python2.4/site-packages/libelf/_libelf.so: undefined symbol: elfx_remscn Apparently, elfutils installed another version of libelf and also overwrote my symlink. It looked to me that the libelf that came with elfutils didn''t have certain symbols that existed in the libelf-0.8.9 I obtained from [1] ?! So, I made the symlink point back to the original libelf that I installed but then I got a different error message: eu-readelf: /usr/lib/libelf.so.1: no version information available (required by eu-readelf) eu-readelf: /usr/lib/libelf.so.1: no version information available (required by eu-readelf) eu-readelf: /usr/lib/libelf.so.1: no version information available (required by eu-readelf) eu-readelf: cannot generate Elf descriptor: Request error: invalid ELF_C_* argument Traceback (most recent call last): File "/usr/bin/dom0cut.py", line 179, in ? main() File "/usr/bin/dom0cut.py", line 137, in main dump = xendump.ElfCore.ElfCoreReader(options.dumpname, options.arch) File "/usr/lib/python2.4/site-packages/xendump/ElfCore.py", line 214, in __init__ raise ValueError, ''section isn\''t found'' ValueError: section isn''t found Any clues on how to deal with this issues ? Will re-compiling eu-readelf ! from source solve this problem ? Did anybody who used kdump with Xen run into the same problem before ? Thanks. [1]: http://www.mr511.de/software/ [2]: http://people.valinux.co.jp/~moriwaka/dumpread/ [3]: http://packages.debian.org/unstable/libs/libelf1 It looks to me that there are 2 different "types" of libelf out there: [1] and the one that comes with elfutils [3] (and maintained by Redhat !?). Regards, Levin Want to change your life? Find the perfect job with Lycos Jobs. Career Advice. Job Resources & Recommendations. Post your resume & find a job match! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel