Yes, you're correct: the latest. And it looks like they;ve updated it already. 
So it's fine.

________________________________
From: Dyninst-api <dyninst-api-boun...@cs.wisc.edu> on behalf of Saija Sorsa 
<sso...@nvidia.com>
Sent: Monday, September 17, 2018 8:23:37 AM
To: John Mellor-Crummey
Cc: dyninst-api@cs.wisc.edu
Subject: Re: [DynInst_API:] libsymtabAPI has undefined reference 
dwarf_next_lines@ELFUTILS_0.173


Hi,



Afaik it actually downloads the latest which is .174 
(https://sourceware.org/elfutils/ftp/). I’m still in the middle of getting the 
version right. Thank you for your help.



From: John Mellor-Crummey <joh...@rice.edu>
Sent: 14 September 2018 17:50
To: Saija Sorsa <sso...@nvidia.com>
Cc: dyninst-api@cs.wisc.edu
Subject: Re: [DynInst_API:] libsymtabAPI has undefined reference 
dwarf_next_lines@ELFUTILS_0.173



You need to download and use the latest elfutils 0.173, which provides this 
function.



This may have been handled automatically in the build configuration if you 
reconfigure with cmake, but I am not sure about that.

--

John Mellor-Crummey



(sent from my phone)

On Sep 14, 2018, at 5:01 AM, Saija Sorsa 
<sso...@nvidia.com<mailto:sso...@nvidia.com>> wrote:

Hi,



I’m new to dyninst, this is the first time I’m using it, please excuse my 
ignorance. I’m having 14.04.1-Ubuntu and I git pulled dyninst and compiled it 
(cmake & cmake install). I have a code that is using dyninstAPI, mostly 
BPatch*. While executing make for the code I get this error:

//usr/local/lib/libsymtabAPI.so.9.3: undefined reference to 
`dwarf_next_lines@ELFUTILS_0.173'



Are you able to help me with this? It smells like a version mismatch / changed 
API in dyninst. Latest git commit for my code is around 6months ago, but the 
dyninst part is even older, if I’m correct. Any debugging suggestions?



Thanks!



________________________________

This email message is for the sole use of the intended recipient(s) and may 
contain confidential information.  Any unauthorized review, use, disclosure or 
distribution is prohibited.  If you are not the intended recipient, please 
contact the sender by reply email and destroy all copies of the original 
message.

________________________________

_______________________________________________
Dyninst-api mailing list
Dyninst-api@cs.wisc.edu<mailto:Dyninst-api@cs.wisc.edu>
https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api
_______________________________________________
Dyninst-api mailing list
Dyninst-api@cs.wisc.edu
https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api

Reply via email to