I don't see new tags in either dyninst.git or docs.git - an oversight?
Yup. I wasn't aware of this new mutator requirement, even as I blissfully
tested pre-8.1. Perhaps I was silently hitting ABI issues and just
getting lucky not to hit anything major...
We weren't either. We hit a weird failure on Fedora 17 that made us look into it. It looks like it's _almost_ safe (which is to say, it isn't) if you don't build C++11x. But since this is mandatory, did you consider enforcing it in the
headers? GCC before 4.7 didn't set __cplusplus correctly, but did have
an experimental flag, so something like this should work portably:
#if !((__cplusplus >= 201103L) || defined(__GXX_EXPERIMENTAL_CXX0X__))
#error "Dyninst requires C++11!"
#endif
If you're ok with that check, but don't want to redo release tarballs, I
may just patch that into the headers for our RPMs.
That is an excellent idea and a lot more friendly than silent segfaults. I'll look into it; repackaging is pretty simple.
Drew
And thank you to Red Hat for hosting the Linux RPMs.
Well, I haven't build 8.1 RPMs just yet. :)
I'll work on getting them soon though. For Fedora I need to coordinate
it with a SystemTap update though, so the distro stays consistent. I
also need to find out if it's ok to bump the library soname in F18. If
not, then only rawhide will get this update officially, but I can still
put new builds in my personal repo as I did before for F17 and EL6.
In any case, I'll send a followup when those builds are available.
Josh
_______________________________________________
Dyninst-api mailing list
Dyninst-api@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api
-- Andrew Bernat Paradyn Project
|
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}