Hi, It would be great if there were info about a mailing list or IRC channel or discussion forum or some other location to ask questions and discuss heaptrack on the Github page. (Or a heaptrack website) I'm wondering two things: 1) Has anyone built heaptrack on a Cray and is there anything special I have to do, since Cray loves to go in and change the OS, and tweak all sorts of things 2) How feasible would it be to port the heaptrack utility (not the gui) to macOS? I may give that a whirl and then create a homebrew formula for it. You won't be able to use heaptrack_gui most likely due to the KDE dependencies, etc, but it would be nice to be able to collect data on macOS, then view on a linux box. Thanks!
Hey, I'll add a reference to the mailing list at heaptrack@kde.org, but there is no real website. 1) I have no personal experience about Cray. Is it running Linux or some other kind of Unix? I suggest you try to compile it and then try to fix the issues you encounter. 2) First of all, KDE is portable to macOS and lots of it is accessible via homebrew afaik. That said, if you don't want to, you don't have to build heaptrack_gui - it's optional. Second, porting heaptrack the tracker to macOS is probably quite some effort. Most notably, there are some Linux-only headers/APIs used which need to be ported. Finally, heaptrack currently only expects and works with ELF executables and DWARF debug information. So you'd have to add support for mach-O and dSYM which is not an easy task. Also, I doubt libunwind works on macOS. But if you find libraries that are similar to libbacktrace and libunwind, one could probably try to port heaptrack. I just wonder - isn't the heap profiler in Instruments pretty decent?
Created attachment 110688 [details] attachment-21692-0.html 1) Yes, it runs craycnl (Cray compute node Linux) which is likely REHL based but I don’t recal at the moment and am not at my computer 2) I know a lot of KDE was accessible through homebrew but they’ve been pruning formulae and consolidating everything into homebrew-core. My quick search didn’t turn anything up, but I only tried “kde” so perhaps I should have been looking for individual components. 2.1) Yeah I suspected that was the case, but thought I’d ask anyway. Thanks for the info and thanks for adding a link to the mailing list. Please feel free to close this issue. On Thu, Feb 15, 2018 at 3:48 AM Milian Wolff <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=390485 > > --- Comment #1 from Milian Wolff <mail@milianw.de> --- > Hey, > > I'll add a reference to the mailing list at heaptrack@kde.org, but there > is no > real website. > > 1) I have no personal experience about Cray. Is it running Linux or some > other > kind of Unix? I suggest you try to compile it and then try to fix the > issues > you encounter. > > 2) First of all, KDE is portable to macOS and lots of it is accessible via > homebrew afaik. That said, if you don't want to, you don't have to build > heaptrack_gui - it's optional. > > Second, porting heaptrack the tracker to macOS is probably quite some > effort. > Most notably, there are some Linux-only headers/APIs used which need to be > ported. Finally, heaptrack currently only expects and works with ELF > executables and DWARF debug information. So you'd have to add support for > mach-O and dSYM which is not an easy task. Also, I doubt libunwind works on > macOS. But if you find libraries that are similar to libbacktrace and > libunwind, one could probably try to port heaptrack. I just wonder - isn't > the > heap profiler in Instruments pretty decent? > > -- > You are receiving this mail because: > You reported the bug.
Cool. Feel free to open bugs about individual issues you face on cray, mac and the like. Cheers