Closed smoge closed 7 months ago
???
Om-Sharp does not even start from the command line. That's all the output I could get so far. It's a Seg Fault All Right.
Finding more about segfault in a Common Lisp binary, especially without access to the professional version of LispWorks, can be challenging. If IS possible, please send me the information and tools.
I'm not a Common Lisp guy.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from om-sharp...
This GDB supports auto-downloading debuginfo from the following URLs:
<https://debuginfod.fedoraproject.org/>
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Downloading separate debug info for /usr/bin/om-sharp
(No debugging symbols found in om-sharp)
Hi, thanks for the bug report.
It would be great if you could provide more details, like OS, version, om-sharp-version/date etc.
needless to say, om-sharp runs as expected here. To be able to debug anything we need some info which tells us where yours and mine system or om-sharp differ
Latest release of om-sharp, on lastest updated release of Fedora Linux. It happens since a few days ago., Is there some tool for debuging I could use to help find out the problem?
Please use the discussion forum for bug-reports, general questions etc.:
https://github.com/cac-t-u-s/om-sharp/discussions/categories/reports
Lets follow up there
I found the problem, after removing, I notice that there were files from the last minor update still in the system, Not sure how they remained there but after removing them, no segfault. The project is nice and dandtyin terms of mem leaks ))). Please close the issue.
(If others had this problems, that might be the same issue)
om-sharp
[1] 44087 segmentation fault (core dumped)