Re: [DynInst_API:] PIE segfault

I am using the "parseThat" program that ships with Dyninst. Executed it as: parseThat --binary-edit=ssh-dyn -i 0 /usr/bin/ssh On Wed, Jun 1, 2016 at 1:07 PM John Detter wrote: > Can you send me the source for the program you're using to do the > rewriting? > -- John > > > On

Re: [DynInst_API:] PIE segfault

No. Ubuntu 16.04 x86_64. On Wed, Jun 1, 2016 at 12:47 PM John Detter wrote: > Mohamed, > > Is this on Windows? > > -- John > > On 5/31/2016 6:25 PM, Mohamed Elsabagh wrote: > > Hi John, > > I pulled the latest commits to master. Now I don't get any errors, but the > resulting

Re: [DynInst_API:] PIE segfault

Mohamed, Is this on Windows? -- John On 5/31/2016 6:25 PM, Mohamed Elsabagh wrote: Hi John, I pulled the latest commits to master. Now I don't get any errors, but the resulting executable file still doesn't run. It gives the same error: "cannot execute binary file: Exec format error."

Re: [DynInst_API:] PIE segfault

Hi John, I pulled the latest commits to master. Now I don't get any errors, but the resulting executable file still doesn't run. It gives the same error: "cannot execute binary file: Exec format error." Any suggestions? Mohamed On Tue, May 31, 2016 at 6:24 PM John Detter

Re: [DynInst_API:] PIE segfault

Hey Mohamed, We found the issue that was causing the assert and we updated the master branch on github. If you want to clone or pull the most recent version it should have the fix for your issue. Let me know if you have any other issues, -- John On 5/31/2016 3:57 PM, Mohamed Elsabagh

Re: [DynInst_API:] PIE segfault

Mohamed git.dyninst.org is now just a mirror and unfortunately it looks like it isn't quite up to date. http://github.com/dyninst/dyninst will get you the latest commits. If you want to update your origin: git remote remove origin git remote add origin

Re: [DynInst_API:] PIE segfault

Hi John, I pulled the latest commit from git.dyninst.org, which resulted in the error in my previous email. Now using a clone from the github path your provided, I am getting the following message on stderr: decodeOneOperand() called with unknown addressing method 18 And even though the output

Re: [DynInst_API:] PIE segfault

Mohamed, Are you sure you are using the latest master? In my version of arch-x86.C line 7993 isn't inside the ia32_decode function. Could you try pulling from master and rebuilding/rerunning? If you could provide another stack trace that would be really helpful. -- John P.S. here is the

Re: [DynInst_API:] PIE segfault

-- >> *From:* Dyninst-api <dyninst-api-boun...@cs.wisc.edu> on behalf of >> Mohamed Elsabagh <melsa...@gmu.edu> >> *Sent:* Friday, May 27, 2016 9:10:51 PM >> *To:* dyninst-api >> *Subject:* [DynInst_API:] PIE segfault >> >> In the latest version

Re: [DynInst_API:] PIE segfault

From:* Dyninst-api <dyninst-api-boun...@cs.wisc.edu> on behalf of > Mohamed Elsabagh <melsa...@gmu.edu> > *Sent:* Friday, May 27, 2016 9:10:51 PM > *To:* dyninst-api > *Subject:* [DynInst_API:] PIE segfault > > In the latest version of Dyninst, rewriting a PIE b

Re: [DynInst_API:] PIE segfault

-api Subject: [DynInst_API:] PIE segfault In the latest version of Dyninst, rewriting a PIE binary (not a library) results in an executable that immediately segfaults. This happens even if no instrumentation was done at all. Simply opening the binary and saving it reproduces the problem. Here's a samp