Re: Add MKCTF
On Wed, Mar 26, 2014 at 11:31 AM, Thor Lancelot Simon t...@panix.com wrote: On Mon, Mar 24, 2014 at 07:27:33PM +0900, Ryota Ozaki wrote: Hi, I'm adding a new build variable MKCTF, which was discussed on the chat some days ago. Currently CTF tools are built and used to generate and manipulate CTF data of ELF binaries when we build with MKDTRACE=yes. Unfortunately, current CTF tools don't work on i386/amd64/arm, and that adds a burden to try DTrace by users. The new variable is intended to separate CTF stuffs from MKDTRACE; we can build DTrace solely without worrying about the CTF issues. Fortunately, CTF data are not used yet by current DTrace of NetBSD, so DTrace still works without CTF data. The CTF data for the kernel are needed in order to use DTrace on the kernel, no? DTrace works anyway w/o CTF data. Nonetheless, it lacks some detailed information. We will of course support CTF data at some point. ozaki-r Thor
Re: Add MKCTF
On Mon, Mar 24, 2014 at 07:27:33PM +0900, Ryota Ozaki wrote: Hi, I'm adding a new build variable MKCTF, which was discussed on the chat some days ago. Currently CTF tools are built and used to generate and manipulate CTF data of ELF binaries when we build with MKDTRACE=yes. Unfortunately, current CTF tools don't work on i386/amd64/arm, and that adds a burden to try DTrace by users. The new variable is intended to separate CTF stuffs from MKDTRACE; we can build DTrace solely without worrying about the CTF issues. Fortunately, CTF data are not used yet by current DTrace of NetBSD, so DTrace still works without CTF data. The CTF data for the kernel are needed in order to use DTrace on the kernel, no? Thor
Re: Add MKCTF
On Tue, Mar 25, 2014 at 1:47 AM, Christos Zoulas chris...@astron.com wrote: In article cakryomjraa3-olqh7wmmqh1tprjzb1oq9a6vrskiin+ltf-...@mail.gmail.com, Ryota Ozaki ozak...@netbsd.org wrote: -=-=-=-=-=- Hi, I'm adding a new build variable MKCTF, which was discussed on the chat some days ago. Currently CTF tools are built and used to generate and manipulate CTF data of ELF binaries when we build with MKDTRACE=yes. Unfortunately, current CTF tools don't work on i386/amd64/arm, and that adds a burden to try DTrace by users. The new variable is intended to separate CTF stuffs from MKDTRACE; we can build DTrace solely without worrying about the CTF issues. Fortunately, CTF data are not used yet by current DTrace of NetBSD, so DTrace still works without CTF data. Once CTF issues are solved, we would be able to merge MKCTF to MKDTRACE again but it would not come soon. So I think the workaround is still useful at this point. My patch is attached and also available at http://www.netbsd.org/~ozaki-r/MKCTF.diff . I am happy with that approach. Thanks! I will commit it later. ozaki-r
