[Arch Linux] Compile error: undefined reference to `dwarf_loclist'

[irth]

Hi, I'm trying to compile dtrace on my Arch Linux x86_64 (kernel 3.9.9-1-ARCH)
But i'm getting a compile error:

../../build/ctfconvert.obj/dwarf.o: In function `die_mem_offset':
/tmp/dtrace/cmd/ctfconvert/dwarf.c:580: undefined reference to `dwarf_loclist'

/tmp/dtrace-bug.1197.txt: http://ix.io/6xY

[dtrace4linux]

Hello Wojciech

it looks like dtrace is detecting an incorrect libdw.a shlib on your system
which doesnt have all the API entry points. for now you can just do a "make
-i" and ignore the ctfdump/ctfconvert tools which wont get built.

On 7 July 2013 18:58, Wojciech Kwolek notifications@github.com wrote:

Hi, i'm trying to compile dtrace on my Arch Linux x86_64 (kernel
3.9.9-1-ARCH)
But i'm getting compile error:

../../build/ctfconvert.obj/dwarf.o: In function die_mem_offset':
/tmp/dtrace/cmd/ctfconvert/dwarf.c:580: undefined reference to
dwarf_loclist'

/tmp/dtrace-bug.1197.txt: http://ix.io/6xY

I had also this problem: http://ix.io/6xX, but I solved it by installing
gcc-multilib.

Sorry for my English, I'm from Poland, and I dont know English very well...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/58
.

[irth]

libdwarf was installed from Arch User Repository.
I tried make -i all, but when I try to load modules:
sudo make load
I'm getting:
/tmp/dtrace$ sudo make load tools/load.pl 19:12:51 Syncing... 19:12:51 Loading: build-3.9.9-1-ARCH/driver/dtracedrv.ko insmod: ERROR: could not load module build-3.9.9-1-ARCH/driver/dtracedrv.ko: No such file or directory /proc/dtrace does not exist. Maybe the driver didnt load properly. make: *** [load] Error 1

[rendaw]

It looks like libdw is included by default on Arch but doesn't include the dwarf_loclist symbol. If you install libdwarf through AUR tools/mkport.pl still finds libdw (around line 335). I just deleted some lines to force libdwarf over libdw.

I didn't hit the compile issue until I installed libdwarf through AUR. If you don't install libdwarf, does the build disable some features or something? I'm not too familiar with the build process.

[rendaw]

Without libdwarf, it appears that the ctfdump/convert stuff is disabled. libdw is installed by default with elfutils.

With libdwarf (from AUR), mkctf.sh fails:

tools/mkctf.sh
ERROR: ctfconvert: die 901: failed to get mem offset location list
ls: cannot access build/linux-3.9.9-1-ARCH.ctf: No such file or directory

There's some discussion on the AUR page about upstream issues, but I'm not sure it's relevant.

[dtrace4linux]

Strange - i took the latest arch download, loaded the deps from the
tools/get-deps-arch script and it built without problem. I need to look at
the libdw vs libdwarf issue - I made changes a while back to be
accomodating of either but it was a dead end - and its annoying. I want to
reexamine ctfdump to see what I could do to omit the dependency. Its
annoying that there are two standard interfaces and not easily
interchangeable.

for now - it mostly doesnt matter - it just means the linux.ctf file is
useless - most people wont care. its only needed for struct member
references in D scripts.

On 13 July 2013 07:26, Rendaw notifications@github.com wrote:

Without libdwarf, it appears that the ctfdump/convert stuff is disabled.
libdw is installed by default with elftools.

With libdwarf (from AUR), mkctf.sh fails:

tools/mkctf.sh
ERROR: ctfconvert: die 901: failed to get mem offset location list
ls: cannot access build/linux-3.9.9-1-ARCH.ctf: No such file or directory

There's some discussion on the AUR page about upstream issues, but I'm not
sure it's relevant.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/58#issuecomment-20915553
.

[rendaw]

I just tried get-deps-arch but I already had all the dependencies and "make all" still didn't build the ctf utils.

To be perfectly honest I've never used dtrace before but it sounded exciting so I wanted to try it. I don't do any D but if you want to get it working and there's any tests/information you need I'd be glad to help.

It seems like with a little work libdw and libdwarf are both available on arch. Are the other distros similar? If it's easier to just support one I think people would be willing to put in a little effort to get whichever dependency is needed.

[dtrace4linux]

If you do "make -i all" then you are good to go - next do:
$ make load
$ sudo build/dtrace -n syscall:::

and you can see all the syscalls on the system (a lot!) You can fine tune,
e.g.

$ sudo build/dtrace -n syscall::open*:'{printf("%s", execname);}'

to see the executables opening files.

libdwarf is the better - but there are lots of versions of this and i was
trying to support all the older systems, so its not so clear cut. My code
is looking to see if libdw and libdwarf is installed and then (probably)
picking the wrong one. When I ran this last night - it was a clean build -
so you likely have both installed and I dont (or I even have neither!)

On 13 July 2013 11:11, Rendaw notifications@github.com wrote:

I just tried get-deps-arch but I already had all the dependencies and
"make all" still didn't build the ctf utils.

To be perfectly honest I've never used dtrace before but it sounded
exciting so I wanted to try it. I don't do any D but if you want to get it
working and there's any tests/information you need I'd be glad to help.

It seems like with a little work libdw and libdwarf are both available on
arch. Are the other distros similar? If it's easier to just support one I
think people would be willing to put in a little effort to get whichever
dependency is needed.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/58#issuecomment-20917773
.

[rendaw]

Ok, thanks for the intro! I'll try that out.

[ryao]

I can reproduce this on Gentoo Linux with the following commands:

# Note that layman must be installed and setup first
layman -a ikelos
echo dev-libs/libdwarf ~amd64 >> /etc/portage/package.accept_keywords
wget 'https://launchpad.net/ubuntu/+archive/primary/+files/dwarfutils_20120410.orig.tar.gz' -O /usr/portage/distfiles/libdwarf-20120410.tar.gz
emerge dev-libs/libdwarf
git checkout git://github.com/dtrace4linux/linux.git
cd linux
make all

It seems that the problem is that the check for libdwarf in tools/mkport.pl is broken. The check will never select libdwarf. Modifying tools/mkport.pl to force libdwarf to be used allows things to work.

As for libelf, this appears to be the commit that broke compatibility:

https://git.fedorahosted.org/cgit/elfutils.git/commit/?id=0cf762c2d960cd64e72d8637db0c38102bd6a4ee

[dtrace4linux]

Thanks for attempting to locate the broken commit. The state of ELF is
forever broken on all kernels because of the horrible history of the two
dwarf libraries. I have given up trying to salvage the horrible nature of
the mess. Its a shame because the owner of libdwarf has done a good job,
but the horrible state of all distros and trying to cater for both ELF
libraries - you can have either or both installed, is really painful.

My next attempt to fix and remove this is to avoid libdwarf and use the
readelf tool instead.

The situation is so bad, because I am always confused whether libdwarf or
libdw is the latest conformant implementation. I have looked at the
implementation of dwarf_loclist but it doesnt help - I tried to create a
portable layer between the two libs but abandoned it due to the "just one
more API needs to be grafted" onboard.

I may take another look (using readelf - or any other tool which works)
since I am now going to look at another kernel bug/issue on ubuntu 12.04.

On 6 March 2014 02:38, Richard Yao notifications@github.com wrote:

Well, it seems that a link with libdw from elfutils is attempted when
libdwarf is installed. Anyway, this is the commit that broke compatibility:

https://git.fedorahosted.org/cgit/elfutils.git/commit/?id=0cf762c2d960cd64e72d8637db0c38102bd6a4ee

Removing libdwarf and downgrading to dev-libs/elfutils-0.148 does not fix
things. We just have a different failure there.

Executing: /home/richard/devel/dtrace/tools/make-me
make -C /lib/modules/3.12.6/build M=/home/richard/devel/dtrace/build-3.12.6/driver
make[2]: *** No targets specified and no makefile found. Stop.
make[1]: *** [kernel] Error 2

Reply to this email directly or view it on GitHubhttps://github.com//issues/58#issuecomment-36819349
.

[gaojx]

I got the same comiple error on centos:
/mnt/disk1/home/gaojx/dtrace/linux/cmd/ctfconvert/dwarf.c:581: undefined reference to `dwarf_loclist'

After command: make -i all, command: dtrace load gives: