[Heaptrack] [Bug 392487] Created file is not compatible with heaptrack

2018-04-20 Thread Jasem Mutlaq
https://bugs.kde.org/show_bug.cgi?id=392487

Jasem Mutlaq  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #8 from Jasem Mutlaq  ---
Ok it appears I need to run: sudo apt-get install zstd which would install the
correct libraries (I used libzstd-dev before which installed older version). At
any rate, now it creates zst file.

It now finally works!

-- 
You are receiving this mail because:
You are watching all bug changes.

[Heaptrack] [Bug 392487] Created file is not compatible with heaptrack

2018-04-20 Thread Jasem Mutlaq
https://bugs.kde.org/show_bug.cgi?id=392487

--- Comment #7 from Jasem Mutlaq  ---
I installed zstd on 16.04 machine but now getting compile errors:

https://paste.kde.org/plj20ityd

-- 
You are receiving this mail because:
You are watching all bug changes.

[Heaptrack] [Bug 392487] Created file is not compatible with heaptrack

2018-04-16 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=392487

--- Comment #6 from Milian Wolff  ---
Oh and one more question: Can you actually attach via GDB? E.g. this part of
the message makes me wonder:

Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf

Try to run `gdb --pid ...` and see if that works for you.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Heaptrack] [Bug 392487] Created file is not compatible with heaptrack

2018-04-16 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=392487

--- Comment #5 from Milian Wolff  ---
do you still see this error:

/usr/bin/heaptrack: 174: [: FALSE: unexpected operator

?

What does this give you in your shell:

echo $SHELL
if [ "TRUE" = "TRUE" ] && [ ! -z "$(which zstd)" ]; then echo "works"; fi

-- 
You are receiving this mail because:
You are watching all bug changes.

[Heaptrack] [Bug 392487] Created file is not compatible with heaptrack

2018-04-14 Thread Jasem Mutlaq
https://bugs.kde.org/show_bug.cgi?id=392487

Jasem Mutlaq  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #4 from Jasem Mutlaq  ---
Nope, I just git pulled and built with zstd support and exactly the same
problem on 16.04. I attached the output as you require but it's exactly same
error message.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Heaptrack] [Bug 392487] Created file is not compatible with heaptrack

2018-04-14 Thread Jasem Mutlaq
https://bugs.kde.org/show_bug.cgi?id=392487

--- Comment #3 from Jasem Mutlaq  ---
Created attachment 112029
  --> https://bugs.kde.org/attachment.cgi?id=112029=edit
heaptrack cat

-- 
You are receiving this mail because:
You are watching all bug changes.

[Heaptrack] [Bug 392487] Created file is not compatible with heaptrack

2018-04-03 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=392487

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Milian Wolff  ---
I think I solved this via

commit 7ae3f595a0ea49abd4b8ecd8a7be2b362e0fa916
Author: Milian Wolff 
Date:   Tue Apr 3 15:30:56 2018 +0200

Make heaptrack.sh file compatible with dash

Don't use the bashism == to compare strings, use = instead.

BUG: 392487

-- 
You are receiving this mail because:
You are watching all bug changes.

[Heaptrack] [Bug 392487] Created file is not compatible with heaptrack

2018-03-30 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=392487

--- Comment #1 from Milian Wolff  ---
Probably a bug I introduced with the addition of zstd support. What shell do
you use? Can you paste the contents of `cat $(which heaptrack)` please - I want
to double-check what it generated.

To workaround this, install zstd development headers, it should both fix this
and make heaptrack faster too :)

-- 
You are receiving this mail because:
You are watching all bug changes.