On 2024/07/07 16:57, Ali Farzanrad wrote:
> I'm really sorry, my files were broken.
> I didn't have any unexpected power outage, so I never expected that my
> files might be broken.
>
> I fixed my files using this command:
>
> # pkg_add -uDsnap -Dinstalled -Dchecksum
Hmm, that's unexpected! I su
I'm really sorry, my files were broken.
I didn't have any unexpected power outage, so I never expected that my
files might be broken.
I fixed my files using this command:
# pkg_add -uDsnap -Dinstalled -Dchecksum
Ali Farzanrad wrote:
> Hi Stuart,
>
> Stuart Henderson wrote:
> > I don't see th
Hi Stuart,
Stuart Henderson wrote:
> I don't see that here.
>
> Firstly, did you run pkg_add -u after updating?
Yes. I also ran this command to ensure everything is up to date:
# pkg_add -uDsnap -Dinstalled
However I couldn't reproduce this error on a clean install on same
computer (Minisforu
I don't see that here.
Firstly, did you run pkg_add -u after updating?
Install the gdb and debug-py3-numpy packages (as well as the debug-python
you already have) and use the 'egdb' binary. The version of gdb in base is
barely useful.
Which cpu architecture? amd64, arm64, sparc64, [...]?
--
I just realized that I have lldb:
$ lldb /usr/local/bin/python3.11
(lldb) target create "/usr/local/bin/python3.11"
Current executable set to '/usr/local/bin/python3.11' (x86_64).
(lldb) run -c 'import numpy'
Process 49716 launched: '/usr/local/bin/python3.11' (x86_64)
Process 49716 stopped
* thre
Hi,
I see this error in latest snapshot:
$ python3.11 -c 'import numpy'
Floating point exception (core dumped)
I installed debug-python package to debug, but I have no idea how to
debug it:
$ gdb -- /usr/local/bin/python3.11
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free
