Re: [DynInst_API:] Type conflict building parseAPI example

["E.Robbins" <er209@xxxxxxxxxx>]

Great, thanks Drew! I will give this a try shortly...

________________________________________
From: Andrew Bernat [bernat@xxxxxxxxxxx]
Sent: 30 January 2013 17:49
To: E.Robbins
Cc: dyninst-api@xxxxxxxxxxx
Subject: Re: [DynInst_API:] Type conflict building parseAPI example

That mistake is on our end. Change it to a Function::blocklist::const_iterator (instead of Function::blocklist::iterator). Or, more easily, use auto. I'll get the documentation updated.

Drew

On Jan 30, 2013, at 10:20 AM, "E.Robbins" <er209@xxxxxxxxxx<mailto:er209@xxxxxxxxxx>> wrote:

Hi there,
I tried to build the simple example from page 3/4 of the parseAPI manual, but it fails with

error: conversion from ‘std::vector<Dyninst::ParseAPI::Edge*>::const_iterator {aka __gnu_cxx::__normal_iterator<Dyninst::ParseAPI::Edge* const*, std::vector<Dyninst::ParseAPI::Edge*> >}’ to non-scalar type ‘std::vector<Dyninst::ParseAPI::Edge*>::iterator {aka __gnu_cxx::__normal_iterator<Dyninst::ParseAPI::Edge**, std::vector<Dyninst::ParseAPI::Edge*> >}’ requested

referring to line 37 of the code listing.

I am building with gcc 4.7.2 on Ubuntu Linux amd64. To build I am using:

g++ -std=c++11 -I/usr/include/boost -g -o recoverCFG recoverCFG.cpp -lparseAPI -lsymtabAPI -linstructionAPI -lcommon -ldynDwarf -ldynElf -ldwarf -lelf -lsymLite

Though I also get the same results using -std=c++0x or when omitting the -std option altogether.

I tried using the pre-built binaries available on the website but then when that failed I checked out the git version, built and tested against that but with the same results.

Am I missing something simple? Can anyone help?

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

--
Andrew Bernat
Paradyn Project
bernat@xxxxxxxxxxx<mailto:bernat@xxxxxxxxxxx>
http://www.cs.wisc.edu/~bernat