Björn Gottschall

For my purpose I did work around this problem by just not using any triggers and tracing every cycle. I just linked my target application into a address range that...

@pgvaz its probably pure luck that the message is not appearing in this case for you. When you look at the code of what you are calling here, the warn...

> this works/around > > ```shell > cat my.tar.zst \ > | zstd --stdout -d - \ > | tar -xf - -C . > ``` No need for a...

Yes, then zstd is consuming symlinks for me. If that is sufficient for you, this ticket should be closed. In my opinion, zstd has inconsistent behavior. Protecting symlinks makes sense...

I just reproduced your code with the following file structure: ``` -rw-rw-r-- 1 user group 135 sep. 26 10:32 myreal.tar.zst lrwxrwxrwx 1 user group 14 sep. 26 10:33 my.tar.zst ->...

The version is not the problem, its something else on your setup: ```shell $ zstd --version *** Zstandard CLI (64-bit) v1.5.5, by Yann Collet *** $ zstd -dc my.tar.zst |...

But just for context, you are not working with symlinks here? How is your code and your workaround related to this issue?