On 04/29/2016 12:35 PM, John Detter wrote:
> Josh,
>
> This was an issue we were seeing with an earlier build of Dyninst. The
> issue was patched on the VEX branch and it should have been merged over
> to master. Do you think you could send me the binary that you are trying
> to parse?
It is
Josh,
This was an issue we were seeing with an earlier build of Dyninst. The
issue was patched on the VEX branch and it should have been merged over
to master. Do you think you could send me the binary that you are trying
to parse?
Also, do you think you could send me the output of "git
On 04/28/2016 06:30 PM, Bill Williams wrote:
> I thought that was fixed on master, but it may not have made it over
> from VEX. Known, and a trivial fix.
Guess I should have sent a quick note before digging in...
I can't see what trivial fix you're expecting though. The assertion I
mentioned
6 7:42:03 PM
To: dyninst-api@cs.wisc.edu
Subject: [DynInst_API:] "Bad addressing mode!" in F23 libm.so
Working with Dyninst master, I'm getting a "Bad addressing mode!"
assertion failed in ia32_decode_operands, parsing F23 libm.so,
specifically from glibc-2.22-11.fc23.x86_64.
Working with Dyninst master, I'm getting a "Bad addressing mode!"
assertion failed in ia32_decode_operands, parsing F23 libm.so,
specifically from glibc-2.22-11.fc23.x86_64. I do have the debuginfo
package for this installed too.
The assertion fails in the default case for switch(op.admet),
