|
From: | anonymous |
Subject: | [Octave-bug-tracker] [bug #61821] segfault using tree_parameter_list in oct file |
Date: | Mon, 17 Jan 2022 09:56:36 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; rv:94.0) Gecko/20100101 Firefox/94.0 |
Follow-up Comment #8, bug #61821 (project octave): Regarding the comment #3: >Is it possible to see your application or package that does not work with the restricted symbol visibility? Sure! I think you have seen it: https://github.com/shsajjadi/OctaveCoder Please consider that I don't want to impose my package and I think there are possibly a limited number of packages that depend on such non public features. Therefor if disabling the visibility makes Octave more faster and reliable go forward and close this issue as won't fix. I think that segfault can be explained by symbol visibility. Both coder and the example encounter segfault permanently. I have relatively limited insight and some of the contents of my previous comment are from googling. My writing skill is also limited, sorry! I periodically fill bugs anonymously and provide some suggestions that some of them has been rejected. Discourse is a good place for such discussions. I can suggest multiple ideas here or on discourse about Octave but discussion should be converted to sensible result (code). I know that there are a few developers here that don't have time even to respond to bug reports. I appreciate your efforts of Octave development. Thank you very much! _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?61821> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |