Re: Help needed: building with -finstrument-functions

> On 11. Nov 2018, at 20:19, Nathan Froyd wrote: > > On Sun, Nov 11, 2018 at 1:25 AM Victor Porof wrote: >> 1. Built this simple trace.cpp: >> https://gist.github.com/victorporof/e9809e33c4dc67ef388672791c4c80cd >> - Used `clang++ trace.cpp -mmacosx-version-min=10.9 -c -o trace.o` >> - I’m bui

Re: Help needed: building with -finstrument-functions

On Sun, Nov 11, 2018 at 1:25 AM Victor Porof wrote: > 1. Built this simple trace.cpp: > https://gist.github.com/victorporof/e9809e33c4dc67ef388672791c4c80cd > - Used `clang++ trace.cpp -mmacosx-version-min=10.9 -c -o trace.o` > - I’m building this without `-finstrument-functions`, obviously. > >

Re: Help needed: building with -finstrument-functions

I’ve linked a prebuilt object that defines `__cyg_profile_func_enter` and `__cyg_profile_func_exit` using LDFLAGS, and that got rid of the initial linker errors. Huzzah! However, now I’m facing other more concerning linker errors: https://gist.github.com/victorporof/55490f49c7b13b4bcfae10ca4f0c

Help needed: building with -finstrument-functions

Hey folks, I’m trying to build Firefox Desktop with `-finstrument-functions`. End goal is doing some exploratory tracing as part of upcoming browser-architecture efforts. What’s the appropriate way of doing this? I tried doing the most naive thing of just passing that flag through CFLAGS and C