Re: Python code error in F39, but not in F38

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Nov 22, 2023 at 5:21 PM Ranjan Maitra via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> On Wed Nov22'23 09:49:49PM, Barry Scott wrote:
> > [...]
> > > On 22 Nov 2023, at 21:32, Barry Scott <barry@xxxxxxxxxxxxxxxx> wrote:
> > >
> > >> Any suggestions as to what is going wrong here?
> > >
> > > At this point you need get more information.
> > >
> > > What do the folllowing GDB commands print?
> > >
> > > p tstate
> > > p tstate->interp
> > > thread allow all bt
> > Doh...
> >
> >       thread apply all bt
> >
> > I always type:
> >       t a a bt
> >
> > and typo'ed the expansion.
>
> Thanks, here is what comes out:
>
>  (gdb)  p tstate->interp
>
>  value has been optimized out
>  (gdb) thread apply all bt
>
>  Thread 1 (Thread 0x7ffff7ec7740 (LWP 387946) "python"):
>  #0  0x00007ffff79e4b5b in _PyInterpreterState_GET () at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118
>  #1  get_state () at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/obmalloc.c:866
>  #2  _PyObject_Free (ctx=<optimized out>, p=0x555556d898a0) at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/obmalloc.c:1850
>  #3  0x00007fff9e5e292f in sip_api_free (mem=<optimized out>) at /usr/src/debug/sip-4.19.25-9.fc39.x86_64/siplib/siplib.c:2239
>  #4  sipOMFinalise (om=0x7fff9e5ff9a0 <cppPyMap.lto_priv.0>) at /usr/src/debug/sip-4.19.25-9.fc39.x86_64/susr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Python/pylifecycle.c:1977

sip-4.19 is from 2018. The Python folks will probably tell you to
update to something newer, like sip-6.7. Also see
<https://pypi.org/project/sip/#history>.

>  #8  0x00007ffff7ab6337 in Py_RunMain () at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Modules/main.c:691
>  #9  0x00007ffff7a7185c in Py_BytesMain (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Modules/main.c:743
>  #10 0x00007ffff764614a in __libc_start_call_main (main=main@entry=0x555555555160

Interesting... You are missing stack frames 5, 6 and 7. You have 0-4,
and 8-10. That may indicate an issue with GDB.

Jeff
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux