On 17/01/2021 21:35, Stestagg wrote:
I would normally agree, except...
This is a refcount issue (I was able to reproduce the problem, gbd shows a
free error )
And I wouldn't recommend DGBing a refcount issue as a beginner to debugging.
The other mailing list identified a PIL bug that messes up
I would normally agree, except...
This is a refcount issue (I was able to reproduce the problem, gbd shows a
free error )
And I wouldn't recommend DGBing a refcount issue as a beginner to debugging.
The other mailing list identified a PIL bug that messes up the refcount for
True, but this refcou
Run python under gdb and when the segv happens use
the gdb bt command to get a stack trace.
Also if gdb says that it needs debug symbols install you will need to
do that. Otherwise the not will not contain symbols.
Barry
> On 17 Jan 2021, at 19:58, Robin Becker wrote:
>
> I have a segfault i
I have a segfault in the 3.10 alpha 4 when running the reportlab document generation; all the other tests seem to have
worked. I would like to ask experts here how to approach getting the location of the problem. I run recent archlinux.
Below is the output of a test run with -Xdev -Xtracemalloc
