Done - thank you for looking into it John.
https://bugs.kde.org/show_bug.cgi?id=383723
Please let me know if there's anything else I can do.
- Andy
On Sat, Aug 19, 2017 at 5:07 PM, John Reiser wrote:
> - (again this is macOS 10.12.x)
>> - in Qt Creator, add a new project
>> - select "Qt Co
- (again this is macOS 10.12.x)
- in Qt Creator, add a new project
- select "Qt Console Application"
- edit its qmake file to remove "CONFIG += console" (this shouldn't be added on
the Mac)
- build "Profile" version
The .pro looks like this:
[[snip]]
Thank you for providing the repro
Thanks John.
"/bin/date" works (which is not surprising as I think workq_ops is related
to threads?)
- (again this is macOS 10.12.x)
- in Qt Creator, add a new project
- select "Qt Console Application"
- edit its qmake file to remove "CONFIG += console" (this shouldn't be
added on the Mac)
- bui
3. This is a Qt-based application
Find the smallest (shortest) executable which triggers the problem.
Does /bin/date work under your callgrind? Does a "null" Qt-based app suffer?
(Something like "BEGIN END;" or "{ }" with "no content": you get the idea.)
Post it here so that anyone can repr
Does anyone have any ideas? Am I doing something incorrectly or missing
something?
Thanks.
- Andy
On Thu, Aug 17, 2017 at 6:15 PM, IMoL wrote:
> 1. macOS 10.12.6
>
> 2. built using git: commit ba17add79a563bd1395dc05fa7309baffbcaa3ce (HEAD
> -> master, origin/master, origin/HEAD)
>
> All I did
1. macOS 10.12.6
2. built using git: commit ba17add79a563bd1395dc05fa7309baffbcaa3ce (HEAD
-> master, origin/master, origin/HEAD)
All I did was clone it, run autogen, run configure with a prefix and make
install
3. This is a Qt-based application
4. When I run callgrind through Qt Creator on my
