> 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
On 06. 06. 22 20:05, Steve Dower wrote:
+1. Glad it's not just me
On 6/6/2022 2:36 PM, Victor Stinner wrote:
First, I understood that "Arbitrary Literal String Type" was adding a
new built-in types for "literal strings" :-) Nope. It's just about
type annotations ;-)
I was also excited
> or has at least agreed to, not sure any releases have happened since I
asked).
I did:
https://www.python.org/downloads/release/python-3110b3/#:~:text=3.11.0b3%20is%20the%20second,support%20the%20new%20feature%20release
.
On Mon, 6 Jun 2022 at 19:13, Steve Dower wrote:
> +1. Glad it's not
> On 6 Jun 2022, at 17:52, Gabriele 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?
+1. Glad it's not just me
On 6/6/2022 2:36 PM, Victor Stinner wrote:
First, I understood that "Arbitrary Literal String Type" was adding a
new built-in types for "literal strings" :-) Nope. It's just about
type annotations ;-)
I was also excited about the new built-in type :-)
Pablo is
The latest bugfix drop for Python 3.10 is here: Python 3.10.5. This release
packs more than 230 bugfixes and docs changes, so you surely want to update
:) You can get it here:
https://www.python.org/downloads/release/python-3105/
## This is the fourth maintenance release of Python 3.10
Python
> Do you know what is involved in the deadlock (as in, what the threads are
> waiting on)?
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. The event is also quite rare and it seems to happen
On Mon, Jun 6, 2022 at 4:35 PM Gabriele wrote:
> The austinp variant is a variant of Austin
> (https://github.com/P403n1x87/austin) for Linux that uses ptrace to
> seize and interrupt/continue threads to capture native stack traces
> using libunwind. During testing, I have discovered that there
Hi Gabriele,
If everything you are doing is pausing and restarting, there should be no
reason
why this would interfere with anything more than if you are doing this at
any other time
other than the interpreter initialization. The only thing I can think of is
that at this stage
locking is much
Hi there
I hope you don't mind me sharing my experience with testing the
austinp variant of Austin with Python >=2.7,<3.11.
The austinp variant is a variant of Austin
(https://github.com/P403n1x87/austin) for Linux that uses ptrace to
seize and interrupt/continue threads to capture native stack
Hi,
Side note: it would be nice to add "typing: " prefix or mention "type
annotation" or "type check" in the title of PEPs which are about that.
Just from the PEP title, it's hard *for me* to guess that it's about
type annotations.
Examples of other PEP titles which confused me:
PEP 612 –
Hello,
With the latest wording changes, PEP 681 – Data Class Transforms is now
fully accepted. Feel free to mark it as such at your convenience.
Happy typing,
— Petr, on behalf of the Steering Council
On 23. 04. 22 13:26, Petr Viktorin wrote:
Hello,
As an initial implementation that will be
Hi,
On buildbots, it's common that we get at least one multiprocessing
test failure per week. While I just reported a new one, I wanted to
add a "expert-multiprocessing" label, but it didn't exist. I just
created the label :-)
https://github.com/python/cpython/labels/expert-multiprocessing
I
13 matches
Mail list logo
