Profiling breaks with error "spawn austin ENOENTaustin process exited with code -4058"

[ckaldemeyer]

I have installed the VS Code extension as described here but it throws an error when I try to profile my code: spawn austin ENOENTaustin process exited with code -4058

How can I get it running?

[P403n1x87]

@ckaldemeyer thanks for your report. This is likely a duplicate of #61. Is the Austin binary installed?

[ckaldemeyer]

Yes. If I run austin in the same venv on a sample test.py file, I get:

venv) PS C:\Users\foo\test> austin -m python test.py
              _   _       
 __ _ _  _ __| |_(_)_ _  
/ _` | || (_-<  _| | ' \ 
\__,_|\_,_/__/\__|_|_||_| 3.6.0 [gcc 12.2.0]
# austin: 3.6.0
# interval: 100
# mode: memory
# memory: 33554432

­ƒÉì Python version: 3.9.13

P21228;T0:2d94 8826880
P21228;T0:2d94 -28672
P21228;T0:2d94 -28672
P21228;T0:2d94 -24576
P21228;T0:2d94 -86016
P21228;T0:2d94 4096

# duration: 5019634

Statistics
Ôîø Sampling duration : 5.02 s
ÔÅ▒´©Å  Frame sampling (min/avg/max) : 95/219/172 ╬╝s
­ƒÉó Long sampling rate : 4/6 (66.67 %) samples took longer than the sampling interval to collect
­ƒÆÇ Error rate : 0/6 (0.00 %) invalid samples

So this seems to work. Any hints?

[ziyuezzy]

I had similar issue, using the default launching (Running 'austin' with args '-i 100 --pipe .../python .../profiling.py'.) failed with error code -2.
But when I do "austin -m .../python .../profiling.py ", it worked