Re: [DynInst_API:] change in getFile from libdwarf to libdw

[John Mellor-Crummey <johnmc@xxxxxxxx>]

follis is Billâs machine :-).

--
John Mellor-Crummey Professor
Dept of Computer Science Rice University
email: johnmc@xxxxxxxx phone: 713-348-5179

On Mar 20, 2018, at 7:23 PM, Sasha Da Rocha Pinheiro <darochapinhe@xxxxxxxx> wrote:

We are downloading and compiling elfutils with dyninst cmake. But my version is 0.168. 

I'll investigate this more.

What is follis? How do I access it?

What do you mean here?  

And of course, some of the path names from /usr/include will
be full paths. But the relative paths from out-of-source builds
will not.

Sasha

---

From: Mark W. Krentel <krentel@xxxxxxxx>
Sent: Tuesday, March 20, 2018 5:52:12 PM
To: Sasha Da Rocha Pinheiro; dyninst-api@xxxxxxxxxxx
Subject: Re: [DynInst_API:] change in getFile from libdwarf to libdw

 

I'm at Xiaozhu's commit b663cf98c97b6 from master as of yesterday,
March 19.  This includes the 84ffda2a8cc commit you mentioned.
I'm still seeing path names like ../../../../src/lib/analysis/Util.cpp.

Perhaps we're not using the same elfutils?  Mine is 0.170.

Make sure you're using a binary from an out-of-source build.  Any of
the x86 hpcstruct binaries from ~krentel/public/binaries on follis
should work.

And of course, some of the path names from /usr/include will
be full paths.  But the relative paths from out-of-source builds 
will not.

--Mark

On 03/20/18 15:46, Sasha Da Rocha Pinheiro wrote:

Hi Mark,

I tested this myself. I am getting the full path with Statement getFile(), with libdw.

Bill told me he remembers doing some change that corrected it at some point. 

I suspect it's the commit 84ffda2a8cca36b1c8f34c4eab9f1319989014ab.

But I'm not sure, this commit has a lot of changes.

What commit are you at that you're getting relative path?

Sasha

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