Mailing List Archive: seg fault in 3.10a4

seg fault in 3.10a4

Jan 17, 2021, 4:52 AM

Post #1 of 6 (111 views)

Not sure if this is where I should report, but I have a segfault in reportlab userguide creation with 3.10a4. I am
getting this info from coredumpctl running archlinux with

Linux hostname 5.10.6-arch1-1 #1 SMP PREEMPT Sat, 09 Jan 2021 18:22:35 +0000 x86_64 GNU/Linux

the error is
Message: Process 1530711 (python) of user 1000 dumped core.

Stack trace of thread 1530711:
#0 0x00007f7c9bf72615 raise (libc.so.6 + 0x3d615)
#1 0x00007f7c9bf5b862 abort (libc.so.6 + 0x26862)
#2 0x00007f7c9bfb45e8 __libc_message (libc.so.6 + 0x7f5e8)
#3 0x00007f7c9bfbc27a malloc_printerr (libc.so.6 + 0x8727a)
#4 0x00007f7c9bfbd64c _int_free (libc.so.6 + 0x8864c)
#5 0x00005631260a01dd n/a (/home/robin/devel/reportlab/.py310/bin/python310 + 0x1401dd)

1) I compile this from source using the standard LTO method my script looks like

###########################################
CFLAGS="-march=x86-64 -mtune=generic -O3 -pipe -fno-plt -fno-semantic-interposition"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -rpath=$HOME/LOCAL/3.10.0a4/lib -fno-semantic-interposition"

./configure \
--prefix=$HOME/LOCAL/3.10.0a4 \
--with-computed-gotos \
--enable-optimizations \
--with-lto \
--enable-ipv6 \
--with-system-expat \
--with-dbmliborder=gdbm:ndbm \
--with-system-ffi \
--with-system-libmpdec \
--enable-loadable-sqlite-extensions && make EXTRA_CFLAGS="$CFLAGS" && make install
###########################################

1) can I get more information using a different compile setup

2) or can I get more information with the python run. I just used
> $ python genuserguide.py
> Built story contains 1843 flowables...
> Saved "/home/robin/devel/reportlab/REPOS/reportlab/docs/reportlab-userguide.pdf"
> free(): invalid pointer
> Aborted (core dumped)

3) I am running in an old style virtual environment generated using a modified virtualenv 16.2.0 (to fix wrong usage of
sys.version[:3] in path names)

4) All other tests seem fine including tests of image generation and the accelerated strinGWidths etc etc so I am a bit
mystified.
--
Robin Becker
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/5DCR2R6POCOHTPFUOY4F5G7GTBYX6OPO/
Code of Conduct: http://python.org/psf/codeofconduct/

Re: seg fault in 3.10a4 [ In reply to ]

stestagg at gmail

Jan 17, 2021, 5:05 AM

Post #2 of 6 (111 views)

Permalink

Hi Robin

It would be ideal if you could please create a new issue here:
https://bugs.python.org/

Thanks

Steve

On Sun, Jan 17, 2021 at 12:53 PM Robin Becker <robin@reportlab.com> wrote:

> Not sure if this is where I should report, but I have a segfault in
> reportlab userguide creation with 3.10a4. I am
> getting this info from coredumpctl running archlinux with
>
> Linux hostname 5.10.6-arch1-1 #1 SMP PREEMPT Sat, 09 Jan 2021 18:22:35
> +0000 x86_64 GNU/Linux
>
>
> the error is
> Message: Process 1530711 (python) of user 1000 dumped core.
>
> Stack trace of thread 1530711:
> #0 0x00007f7c9bf72615 raise (libc.so.6 + 0x3d615)
> #1 0x00007f7c9bf5b862 abort (libc.so.6 + 0x26862)
> #2 0x00007f7c9bfb45e8 __libc_message (libc.so.6 +
> 0x7f5e8)
> #3 0x00007f7c9bfbc27a malloc_printerr (libc.so.6 +
> 0x8727a)
> #4 0x00007f7c9bfbd64c _int_free (libc.so.6 + 0x8864c)
> #5 0x00005631260a01dd n/a
> (/home/robin/devel/reportlab/.py310/bin/python310 + 0x1401dd)
>
> 1) I compile this from source using the standard LTO method my script
> looks like
>
> ###########################################
> CFLAGS="-march=x86-64 -mtune=generic -O3 -pipe -fno-plt
> -fno-semantic-interposition"
> LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now
> -rpath=$HOME/LOCAL/3.10.0a4/lib -fno-semantic-interposition"
>
>
> ./configure \
> --prefix=$HOME/LOCAL/3.10.0a4 \
> --with-computed-gotos \
> --enable-optimizations \
> --with-lto \
> --enable-ipv6 \
> --with-system-expat \
> --with-dbmliborder=gdbm:ndbm \
> --with-system-ffi \
> --with-system-libmpdec \
> --enable-loadable-sqlite-extensions && make
> EXTRA_CFLAGS="$CFLAGS" && make install
> ###########################################
>
> 1) can I get more information using a different compile setup
>
> 2) or can I get more information with the python run. I just used
> > $ python genuserguide.py
> > Built story contains 1843 flowables...
> > Saved
> "/home/robin/devel/reportlab/REPOS/reportlab/docs/reportlab-userguide.pdf"
> > free(): invalid pointer
> > Aborted (core dumped)
>
> 3) I am running in an old style virtual environment generated using a
> modified virtualenv 16.2.0 (to fix wrong usage of
> sys.version[:3] in path names)
>
> 4) All other tests seem fine including tests of image generation and the
> accelerated strinGWidths etc etc so I am a bit
> mystified.
> --
> Robin Becker
> _______________________________________________
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-leave@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/5DCR2R6POCOHTPFUOY4F5G7GTBYX6OPO/
> Code of Conduct: http://python.org/psf/codeofconduct/
>

Re: seg fault in 3.10a4 [ In reply to ]

tjreedy at udel

Jan 17, 2021, 5:49 AM

Post #3 of 6 (111 views)

Permalink

On 1/17/2021 8:05 AM, Stestagg wrote:
> Hi Robin
>
> It would be ideal if you could please create a new issue here:
> https://bugs.python.org/ <https://bugs.python.org/>

If 'reportlab userguide creation' uses any 3rd party compiled C code,
this may be premature. bugs.python.org is for patching cpython. Seg
faults with 3rd party extensions are often, even usually due to a bug in
the extension that we cannot fix, or for new python version, a missing
upgrade.

The questions Robin asked seem like a reasonable start. He might get
additional suggestions from python-list from someone who has seen
something similar.

--
Terry Jan Reedy
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/6SRTWMOHBGKPXTTUBSU477YEPOZSJR46/
Code of Conduct: http://python.org/psf/codeofconduct/

Re: seg fault in 3.10a4 [ In reply to ]

robin at reportlab

Jan 17, 2021, 7:51 AM

Post #4 of 6 (111 views)

Permalink

On 17/01/2021 13:49, Terry Reedy wrote:
> On 1/17/2021 8:05 AM, Stestagg wrote:
>> Hi Robin
>>
>> It would be ideal if you could please create a new issue here: https://bugs.python.org/ <https://bugs.python.org/>
>
> If 'reportlab userguide creation' uses any 3rd party compiled C code, this may be premature. bugs.python.org is for
> patching cpython. Seg faults with 3rd party extensions are often, even usually due to a bug in the extension that we
> cannot fix, or for new python version, a missing upgrade.
>
> The questions Robin asked seem like a reasonable start. He might get additional suggestions from python-list from
> someone who has seen something similar.
>
Thanks, we have two C extensions & pillow so I will do as you suggest and ask in the python list for debugging advice.
--
Robin Becker
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/4R72YLNH2LFNCOOEXQAF3Q2MBHEKMAPU/
Code of Conduct: http://python.org/psf/codeofconduct/

Re: seg fault in 3.10a4 [ In reply to ]

vstinner at python

Jan 17, 2021, 8:54 AM

Post #5 of 6 (110 views)

Permalink

See https://github.com/python-pillow/Pillow/issues/5193 and
https://github.com/python-pillow/Pillow/pull/5194 for a Pillow crash
on Python 3.10. A fix is merged in master, but there is no release
containing the fix yet.
https://github.com/python-pillow/Pillow/commit/543fa2ceb78103c7ae098900c315748a9283e4d4

Victor

On Sun, Jan 17, 2021 at 4:55 PM Robin Becker <robin@reportlab.com> wrote:
>
> On 17/01/2021 13:49, Terry Reedy wrote:
> > On 1/17/2021 8:05 AM, Stestagg wrote:
> >> Hi Robin
> >>
> >> It would be ideal if you could please create a new issue here: https://bugs.python.org/ <https://bugs.python.org/>
> >
> > If 'reportlab userguide creation' uses any 3rd party compiled C code, this may be premature. bugs.python.org is for
> > patching cpython. Seg faults with 3rd party extensions are often, even usually due to a bug in the extension that we
> > cannot fix, or for new python version, a missing upgrade.
> >
> > The questions Robin asked seem like a reasonable start. He might get additional suggestions from python-list from
> > someone who has seen something similar.
> >
> Thanks, we have two C extensions & pillow so I will do as you suggest and ask in the python list for debugging advice.
> --
> Robin Becker
> _______________________________________________
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-leave@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/4R72YLNH2LFNCOOEXQAF3Q2MBHEKMAPU/
> Code of Conduct: http://python.org/psf/codeofconduct/

--
Night gathers, and now my watch begins. It shall not end until my death.
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/BHNEMVPHGDGGNMWI5KRLNIKRCLCYH5NT/
Code of Conduct: http://python.org/psf/codeofconduct/

Re: seg fault in 3.10a4 [ In reply to ]

robin at reportlab

Jan 17, 2021, 10:07 AM

Post #6 of 6 (110 views)

Permalink

On 17/01/2021 16:54, Victor Stinner wrote:
> See https://github.com/python-pillow/Pillow/issues/5193 and
> https://github.com/python-pillow/Pillow/pull/5194 for a Pillow crash
> on Python 3.10. A fix is merged in master, but there is no release
> containing the fix yet.
> https://github.com/python-pillow/Pillow/commit/543fa2ceb78103c7ae098900c315748a9283e4d4
>
> Victor
Thanks for that. I might try to build pillow from git and see if that helps.

.......--
Robin Becker
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/JMQ25DF4OW7JRMU5Y6D6UDFXOCTDIRFB/
Code of Conduct: http://python.org/psf/codeofconduct/