[libunwind] RE: Problems using unw_remote_init

[David Mosberger]

>>>>> On Wed, 25 Aug 2004 15:58:01 +0100, "Thomas Hallgren" <address@hidden> 
>>>>> said:

  >> That should be OK.  Actually, I don't think you'd need -lunwind.
  >> Or do you get unresolved symbols without it?  That might be
  >> indicative of a problem (though not necessarily so).
  >> 
  Thomas> If I try to link without the -lunwind I get the following
  Thomas> errors:

  Thomas> threads/context/context_posix_ia64.o(.text+0x1222): In
  Thomas> function `osCtxtRAW':
  Thomas> ../../../../src/jvm/threads/context/context_posix_ia64.c:241:
  Thomas> undefined reference to `_Uia64_getcontext'

  Thomas> 
/home/thallgre/libunwind/src/.libs/libunwind-ia64.a(Ginit.o)(.text+0x1b1
  Thomas> 2): In function `get_dyn_info_list_addr': ia64/Ginit.c:105:
  Thomas> undefined reference to `_U_dyn_info_list_addr'

  Thomas> 
/home/thallgre/libunwind/src/.libs/libunwind-ia64.a(Ginit.o)(.text+0x260
  Thomas> 2): In function `get_static_proc_name': ia64/Ginit.c:385:
  Thomas> undefined reference to `_Uelf64_get_proc_name'

  Thomas> 
/home/thallgre/libunwind/src/.libs/libunwind-ia64.a(Gfind_dynamic_proc_i
  Thomas> nfo.o)(.text+0x1d2): In function `local_find_proc_info':
  Thomas> mi/Gfind_dynamic_proc_info.c:49: undefined reference to
  Thomas> `_U_dyn_info_list_addr'

Hmmh, those dependencies look OK.  Do you have a self-contained
minimal test that reproduces the problem?

        --david