The soon-to-be-merged Core refactor (see #14) seems to no longer work with PerfFlow Aspect (PFA). When using both PFA and DYAD's wrapper library (libdyad_sync.so), applications seem to hang.
I'm not yet certain why this happens, but it likely has to do with the fact that both PFA's C API and DYAD's wrapper library use __atribute__((constructor)). That likely means that, if PFA and DYAD are linked/loaded in the wrong order, things will break. Combine that with the fact that DYAD's wrapper library uses the preload trick, and it's pretty likely that things are being loaded incorrectly.
JaeseungYeom
commented
1 year ago
The soon-to-be-merged Core refactor (see #14) seems to no longer work with PerfFlow Aspect (PFA). When using both PFA and DYAD's wrapper library (
libdyad_sync.so), applications seem to hang.I'm not yet certain why this happens, but it likely has to do with the fact that both PFA's C API and DYAD's wrapper library use
__atribute__((constructor)). That likely means that, if PFA and DYAD are linked/loaded in the wrong order, things will break. Combine that with the fact that DYAD's wrapper library uses the preload trick, and it's pretty likely that things are being loaded incorrectly.