Open pwittich opened 2 months ago
Hi @pwittich ! Python code can't generate segmentation fault by itself. This is an issue with the Python interpreter and/or some lowl level library
ok, well, here is the output from lldb
. It's in the cleanup of python itself.
(elec) [dev_board] which python 7:17:51
/Users/wittich/miniconda3/envs/elec/bin/python
(elec) [dev_board] lldb `which python` 7:18:53
(lldb) target create "/Users/wittich/miniconda3/envs/elec/bin/python"
Current executable set to '/Users/wittich/miniconda3/envs/elec/bin/python' (arm64).
(lldb) run /Users/wittich/miniconda3/envs/elec/bin/kicost --version
Process 37036 launched: '/Users/wittich/miniconda3/envs/elec/bin/python' (arm64)
KiCost v1.1.19
Process 37036 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x10)
frame #0: 0x00000001000f1ce0 python`_PyObject_Free + 40
python`:
-> 0x1000f1ce0 <+40>: ldr x19, [x8, #0x10]
0x1000f1ce4 <+44>: adrp x8, 1092
0x1000f1ce8 <+48>: ldr x8, [x8, #0x7f8]
0x1000f1cec <+52>: cmp x8, x19
Target 0: (python) stopped.
(lldb)
Anyhow, if you want to close this, go ahead.
kicost
crashes after successfully running on Macos Sonoma 14.6.1, using an anaconda environment. I can reproduce the crash w/o even processing a file (see below). "Successfully running" means that the xlsx file is generated and is readable by Excel. So it is not an issue per se, though it is maybe concerning.See below.
Installed via pip in the virtual environment;