On 10/19/2015 02:43 PM, Bill Williams wrote:
* Shared libraries are now consistent with executables: .o files are
modules/mapped_modules, and they are contained in objects/mapped_objects.
How are dynamic library callbacks working under this? We talked about
changing this to report BPatch_object, but you can't really do that
without breaking API and ABI.
If you're using BPatch_module, BPatch_object, Symtab::Module, or
Symtab::Object on shared libraries, *please* test this out and let me
know what interfaces on the object classes should be there and aren't
(and whether this change is a horrible backwards compatibility breaker).
Please don't try to balance horribleness -- just don't break at all
without exceptional justification. Looking at the public header
changes, I don't think there's anything here that can't wait until the
next soname. If you're itching badly, bring on 9.1 sooner.
_______________________________________________
Dyninst-api mailing list
Dyninst-api@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api