On 18/11/2025 14:56, Thomas Schmitt wrote:
Max Nikulin wrote:I had an idea to have a look into strace sources. First step was to locate its upstream repository, so "apt show strace". At <https://strace.io/> I have noticed*Print paths and more info associated with file descriptors.*But my wodim strace output is not showing the paths already before they get associated with a file descriptor.
Then my next idea is that addresses are pointers to garbage instead of to c strings. I would try gdb or tools like ASAN & Co (sanitizers) and valgrind with hope to get warnings related to reading of uninitialized memory or writing outside of allocated chunks.
Is there anything interesting in call stacks?
strace -k -e trace=openat wodim --devices
(unsure if installing debug symbols may help strace)