On Sun Dec03'23 01:51:24PM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Sun, 3 Dec 2023 13:51:24 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: Python code error in F39, but not in F38
>
> On 11/19/23 08:2
On 11/19/23 08:25, Ranjan Maitra via users wrote:
I was running the code here:
https://github.com/maitra/Visual-Information-Fidelity---Python3
However, the code runs in F38 (python 3.11) without error, but not in F39
(python 3.12) where it
ends with a segmentation fault (after doing the calcul
On Sun Dec03'23 01:47:46PM, Barry Scott wrote:
> From: Barry Scott
> Date: Sun, 3 Dec 2023 13:47:46 +
> To: Community support for Fedora users
> CC: Ranjan Maitra
> Reply-To: Community support for Fedora users
> Subject: Re: Python code error in F39, but not in F38
On Sun Dec03'23 09:38:20AM, Jeffrey Walton wrote:
> From: Jeffrey Walton
> Date: Sun, 3 Dec 2023 09:38:20 -0500
> To: Community support for Fedora users
> CC: Ranjan Maitra
> Reply-To: noloa...@gmail.com, Community support for Fedora users
>
> Subject: Re: Python cod
On Wed, Nov 22, 2023 at 5:21 PM Ranjan Maitra via users
wrote:
>
> On Wed Nov22'23 09:49:49PM, Barry Scott wrote:
> > [...]
> > > On 22 Nov 2023, at 21:32, Barry Scott wrote:
> > >
> > >> Any suggestions as to what is going wrong here?
> > >
> > > At this point you need get more information.
> >
> On 2 Dec 2023, at 15:24, Ranjan Maitra via users
> wrote:
>
> However, the following:
> /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118
> file is where the segfault is, and that is in python3-devel. Perhaps I just
> report it there and see where that
On Sat Dec02'23 09:34:08AM, Barry Scott wrote:
> From: Barry Scott
> Date: Sat, 2 Dec 2023 09:34:08 +
> To: Community support for Fedora users
> CC: Ranjan Maitra
> Reply-To: Community support for Fedora users
> Subject: Re: Python code error in F39, but not in F38
> On 1 Dec 2023, at 03:44, Ranjan Maitra via users
> wrote:
>
> So, it seems, so is this a bug that needs to be reported?
Start by reporting on fedora bugzilla against the sip package with all the info
you have collected in this email thread.
Barry
--
__
itra via users
> Date: Thu, 23 Nov 2023 08:18:05 -0600
> To: Community support for Fedora users
> Cc: Ranjan Maitra
> Reply-To: Community support for Fedora users
> Subject: Re: Python code error in F39, but not in F38
>
> On Thu Nov23'23 08:28:36AM, Barry wrote:
> >
On Fri, Nov 24, 2023 at 5:01 PM Roger Heflin wrote:
> I have seen the bug in old code that a new compiler
> optimization/library fix exposed.
> [...]
> I also previously worked for a company that compiled their code with 3
> different bought linux compilers, and a SGI and Sun compiler and
> exami
I have seen the bug in old code that a new compiler
optimization/library fix exposed.
I have seen code unload a loadable library and then turn around and
call a function in the unloaded library (it worked since the unload
was a NOOP), but broke when the vendor removed/fixed the NOOP and
made the
> On 23 Nov 2023, at 14:18, Ranjan Maitra via users
> wrote:
>
> One aspect to note is that the C code (not by me) is from 1988, though last
> updated in 1997. It is not clear to me if that is a plus (because programmers
> had the time to be more careful in those days) or a minus (because mo
On Thu Nov23'23 08:28:36AM, Barry wrote:
> From: Barry
> Date: Thu, 23 Nov 2023 08:28:36 +
> To: Community support for Fedora users
> CC: Ranjan Maitra
> Reply-To: Community support for Fedora users
> Subject: Re: Python code error in F39, but not in F38
>
>
&
> On 22 Nov 2023, at 22:21, Ranjan Maitra via users
> wrote:
>
> #4 sipOMFinalise (om=0x7fff9e5ff9a0 ) at /usr/src/debug/
It is a bug in the sip code is my strong expectation.
I would also guess that tstate is likely 0 and causing a SEGV.
What did sip do to damage the tstate (thread state I
On Wed Nov22'23 02:36:35PM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Wed, 22 Nov 2023 14:36:35 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: Python code error in F39, but not in F38
>
> On 11/22/23 14:2
On 11/22/23 14:20, Ranjan Maitra via users wrote:
On Wed Nov22'23 09:49:49PM, Barry Scott wrote:
From: Barry Scott
Date: Wed, 22 Nov 2023 21:49:49 +
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.
On Wed Nov22'23 09:49:49PM, Barry Scott wrote:
> From: Barry Scott
> Date: Wed, 22 Nov 2023 21:49:49 +
> To: Community support for Fedora users
> CC: Ranjan Maitra
> Reply-To: Community support for Fedora users
> Subject: Re: Python code error in F39, but not in
> On 22 Nov 2023, at 21:32, Barry Scott 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 alw
> On 22 Nov 2023, at 20:16, Ranjan Maitra via users
> wrote:
>
> Thanks very much for this for explaining how to run gdb on a python script!
> On Python 3.12 (Fedora 39), I get, at the very end:
>
> Thread 1 "python" received signal SIGSEGV, Segmentation fault.
> 0x779e4b5b in _PyInt
On Tue Nov21'23 05:25:35PM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Tue, 21 Nov 2023 17:25:35 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: Python code error in F39, but not in F38
>
> On 11/19/23 10:0
> On 22 Nov 2023, at 16:14, Ranjan Maitra via users
> wrote:
>
> Thanks! Interesting, I wonder if that is also what has caused tensorflow to
> not go up to 3.12 for now.
Complex packages usually take a while to port to a new python is released.
All the python packages that fedora ships have
On Wed Nov22'23 08:12:58AM, George N. White III wrote:
> From: "George N. White III"
> Date: Wed, 22 Nov 2023 08:12:58 -0400
> To: Community support for Fedora users
> Reply-To: Community support for Fedora users
> Subject: Re: Python code error in F39, but not i
On Sun, Nov 19, 2023 at 2:02 PM Ranjan Maitra via users <
users@lists.fedoraproject.org> wrote:
> On Sun Nov19'23 05:35:19PM, Barry wrote:
> > From: Barry
> > Date: Sun, 19 Nov 2023 17:35:19 +
> > To: Community support for Fedora users
> >
> > >
> > >
> > > It is possible that there is a bu
On 11/19/23 10:01, Ranjan Maitra via users wrote:
I tried:
$ gdb python "./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7"
(gdb)
$ gdb python
(gdb) run ./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7
--
___
users mailing list -- users@lists.fedora
Start gdb python. Set a breakpoint in the shared module. continue.
On Sun, Nov 19, 2023 at 1:02 PM Ranjan Maitra via users <
users@lists.fedoraproject.org> wrote:
> On Sun Nov19'23 05:35:19PM, Barry wrote:
> > From: Barry
> > Date: Sun, 19 Nov 2023 17:35:19 +
> > To: Community support for
On Sun Nov19'23 05:35:19PM, Barry wrote:
> From: Barry
> Date: Sun, 19 Nov 2023 17:35:19 +
> To: Community support for Fedora users
>
> >
> >
> > It is possible that there is a bug in the code itself, but nothing above
> > points to my created code.
> >
> > Any suggestions? Or is this a bug?
> On 19 Nov 2023, at 16:26, Ranjan Maitra via users
> wrote:
>
> Hi,
>
> I was running the code here:
> https://github.com/maitra/Visual-Information-Fidelity---Python3
>
> However, the code runs in F38 (python 3.11) without error, but not in F39
> (python 3.12) where it
> ends with a segm
Hi,
I was running the code here:
https://github.com/maitra/Visual-Information-Fidelity---Python3
However, the code runs in F38 (python 3.11) without error, but not in F39
(python 3.12) where it
ends with a segmentation fault (after doing the calculations).
Both, however, give an answer that ar
28 matches
Mail list logo
