libunwind-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libunwind-devel] Build glibc linking libunwind


From: Ken Werner
Subject: Re: [Libunwind-devel] Build glibc linking libunwind
Date: Thu, 13 Oct 2011 16:33:16 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1

On 10/13/2011 04:22 PM, Ken Werner wrote:
On 10/12/2011 04:40 PM, Paul Pluzhnikov wrote:
On Wed, Oct 12, 2011 at 4:14 AM, Ken Werner<address@hidden> wrote:
On 09/24/2011 11:46 PM, Fabio wrote:

Hi all,
I am trying to build glibc and link libunwind to get a backtrace at
the beginning of some glibc function like strcpy for example but I
can't get them to build.
I include -lunwind in the CFLAGS and I export
LD_LIBRARY_PATH=/usr/local/lib, but when it comes to build ld.so it
fails:

/home/wintermute/tesi/glibc/2.14/custom/glibc-2.14/string/strcpy.c:43:
undefined reference to `_Ux86_getcontext'
/home/wintermute/tesi/glibc/2.14/custom/glibc-2.14/string/strcpy.c:44:
undefined reference to `_ULx86_init_local'
collect2: ld returned 1 exit status

Am I missing something? Sorry for asking a dumb question and thanks in
advance.

I suspect you're on a system where the linker does not pull in indirect
shared libs (the default behavior of recent Debian or Fedora based
distros).
I had a similar issue - see:
http://lists.gnu.org/archive/html/libunwind-devel/2011-03/msg00002.html.
You're probably just missing to link against libunwind-x86_64.so. Adding
-lunwind-x86 to your CLFAGS/LDFLAGS should be sufficient.

The link failure is while linking ld.so itself. It better not use
libunwind-x86_64.so (or any other shared library) for obvious reasons.

Oh, ok. So, you modified strcpy.c of glibc to make use of
functionalities provided by libunwind. And it looks like strcpy.c gets
also pulled in when the ld.so is being built. Maybe you can ifdef the
code that uses libunwind functionalities.

A colleague just suggested to test for the NOT_IN_libc define which is set by the build system.

Regards
Ken



reply via email to

[Prev in Thread] Current Thread [Next in Thread]