Re: Deadlock when interrupting interpreter initialisation with ptrace?

> Don't you have the backtrace from libunwind that you could save from austinp itself?

Unfortunately no as the "deadlock" happens before any samples have a
chance to be collected. Upon further investigation, it seems that
trying to resume a thread over and over when ptrace fails takes quite
"some" time (in fact, more than I'd have hoped). Playing with a larger
wait timeout (100 ms, but the largest number I've seen so far on my
machine is 4 ms, which is still an eternity compared to a sensible
sampling interval of 10 ms) seems to "cure" the problem, which I've
only seen during interpreter initialisation. So perhaps Python itself
is off the hook!

On Mon, 6 Jun 2022 at 19:20, Barry Scott <[email protected]> wrote:
>
>
>
> On 6 Jun 2022, at 17:52, Gabriele <[email protected]> wrote:
>
> I've found it hard to give an answer to this question. Because austinp
> is already tracing the interpreter, I cannot use, e.g., gdb to dump a
> backtrace.
>
>
> Don't you have the backtrace from libunwind that you could save from austinp itself?
>
> Barry
>


-- 
"Egli è scritto in lingua matematica, e i caratteri son triangoli,
cerchi, ed altre figure
geometriche, senza i quali mezzi è impossibile a intenderne umanamente parola;
senza questi è un aggirarsi vanamente per un oscuro laberinto."

-- G. Galilei, Il saggiatore.
_______________________________________________
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at https://mail.python.org/archives/list/[email protected]/message/Y2GHXXQGJ6CNHHIO6DVERKWKDRUCOQIR/
Code of Conduct: http://python.org/psf/codeofconduct/