Re: [DynInst_API:] status of dyninstRTExport.h

[Andrew Bernat <bernat@xxxxxxxxxxx>]

Okay, that file is partially correct. 

The DYNINSTuserMessage function is there and there is a test for it in the test suite, so I would expect it to work. Of the thread stuff, setNewthrCB does nothing (and will be removed), but the rest of the functions have implementations. 

I'll get this added to the header file list. I think we just overlooked it. 

Drew

On Aug 22, 2012, at 8:02 PM, Andrew Bernat <bernat@xxxxxxxxxxx> wrote:

I'll look into it, and I'll let you know tomorrow. 

Drew

On Aug 21, 2012, at 8:53 PM, Josh Stone <jistone@xxxxxxxxxx> wrote:

Hi,

What is the status of dyninstRTExport.h?  Is this meant to be generally
available, and if so shouldn't it be part of "make install"?

I'm exploring ways to implement a data channel between mutator/mutatee,
and DYNINSTuserMessage() looks like it could be a winner.  If using this
is ok, are there any caveats with it?  What other options do people
choose to send data back to the mutator?

For that matter, what would be recommended for the reverse?  Just a
oneTimeCode funcCall snippet with some mutatee-allocated variable?

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

--

Andrew Bernat

Paradyn Project

bernat@xxxxxxxxxxx

http://www.cs.wisc.edu/~bernat

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

--

Andrew Bernat

Paradyn Project

bernat@xxxxxxxxxxx

http://www.cs.wisc.edu/~bernat