Heaptrack traces all memory allocations and annotates these events with stack
traces. Dedicated analysis tools then allow you to interpret the heap memory
profile to:
* find hotspots that need to be optimized to reduce the memory footprint of
your application
* find memory leaks, i.e. locations that allocate memory which is never
deallocated
* find allocation hotspots, i.e. code locations that trigger a lot of
memory allocation calls
* find temporary allocations, which are allocations that are directly
followed by their deallocation
Mk/Uses: always use colon for build/run suffix
Most USES use a colon for build/run(/test) suffixes. Change kde.mk,
qt.mk and pyqt.mk to do the same, and update all ports using that.
Document in CHANGES.
PR: 266034
Exp-run by: antoine
Approved by: tcberner (mentor)
Differential Revision: https://reviews.freebsd.org/D36349
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
devel/heaptrack: fix build on 14-
On 14-, libunwind doesn't install a corresponding <unwind.h>.
It doesn't seem to be necessary, either: builds fine on
13- and 14- without the extra check in heaptrack.
devel/heaptrack: update to 1.3.0, latest upstream
Heaptrack traces all memory allocations and annotates these events with
stack traces. Dedicated analysis tools then allow you to interpret the
heap memory profile to, e.g., find hotspots that need to be optimized
to reduce the memory footprint of your application.
Release notes are here:
https://invent.kde.org/sdk/heaptrack/-/releases/v1.3.0
Version 1.3.0 comes with quite some important new features, notably
time based filtering capabilities and support for custom suppressions.
KDE_INVENT: drop WRKSRC hack
When USE_GITLAB was changed to follow upstream GitLab's change
in the way tag-tarballs were delivered, a hack was added to
KDE_INVENT because **that** GitLab installation lagged behind
(by one minor revision, Ithink). Now KDE's installation has
been upgraded, it had the same tag-tarball layout as other
GitLabs and the hack is no longer needed.
The ports that use KDE_INVENT have their distinfo updated,
but the ports themselves do not change so I'm not bumping
PORTREVISION; it's the same git checkout, just with different
icing on top.
Fix devel/heaptrack on i386 (32-bit ELF), I hope
This patch was removed in the previous update, but was still
necessary. I have since submitted it upstream.
Reported by: fallout
Update devel/heaptrack some more
There were patches from Greg V upstream to fix the build of 1.2.0
on FreeBSD, so just chase KDE_INVENT up to that version. This
means we can drop our patches, and it fixes plist issues from my
previous update as well.
Use KDE_INVENT where appropriate
KDE ports that use unreleased versions / versions straight from git.
PORTVERSION or DISTVERSION increased:
- audio/amarok has a newer tag so the commit hash jumps.
- devel/heaptrack has a newer tag so the commit hash jumps.
- graphics/kooka advances to a newer commit, nothing spectacular.
- graphics/peruse advances a great deal to its current state, which
is slightly-before-a-real-release. This one will be dropping KDE_INVENT
and going to normally-released soon, says upstream.
- net/smb4k has a newer tag so the commit hash jumps.
PORTVERSION unchanged, but I didn't bump PORTREVISION either
because it's the same software:
(Only the first 15 lines of the commit message are shown above )
devel/heaptrack Try to fix 32-bit build
I don't see that this can ever have built on 32-bit FreeBSD (i386
in particular) because the code uses Sxword, which our elf32.h
doesn't define. The Linux elf.h (which hanbles both sizes) does
define a 64-bit Sxword.
The patch throws in a using (typedef, but C++-style) that mimics
the 64-bit integers used in the Linux headers; this 64-bit value
doesn't match the size of Elf32_Dyn fields in either OS, but
I'll take a warning over non-stop build failures any day.
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
devel/heaptrack: fix build with GCC-based architectures
Add USES=compiler:c++11-lang to fix build:
Your compiler is too old and does not support the required C++11 features.
Approved by: mentors (implicite approval)
New port: devel/heaptrack
- At the moment this includes only the GUI part and not the actual tracker.
Heaptrack traces all memory allocations and annotates these events with stack
traces. Dedicated analysis tools then allow you to interpret the heap memory
profile to:
* find hotspots that need to be optimized to reduce the memory footprint of
your application
* find memory leaks, i.e. locations that allocate memory which is never
deallocated
* find allocation hotspots, i.e. code locations that trigger a lot of
memory allocation calls
* find temporary allocations, which are allocations that are directly
followed by their deallocation
WWW: https://github.com/KDE/heaptrack
