[MacPorts] #24860: 'quit' and 'exit' do not work well for octave
#24860: 'quit' and 'exit' do not work well for octave ----------------------------+----------------------------------------------- Reporter: qchen3@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: quit, exit | Port: octave ----------------------------+----------------------------------------------- I found it is always painful to quit or exit octave, current 3.2.4, as well as 3.2.3. Up quitting or exiting, it will give me the following messages: ********************************************* octave:1> quit panic: Segmentation fault -- stopping myself... attempting to save variables to `octave-core'... save to `octave-core' complete Segmentation fault ********************************************* Ctr-D, quit, exit behave the same way, that is, give me the same error messages. -- Ticket URL: <http://trac.macports.org/ticket/24860> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24860: 'quit' and 'exit' do not work well for octave ----------------------------+----------------------------------------------- Reporter: qchen3@… | Owner: stechert@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: octave ----------------------------+----------------------------------------------- Changes (by jmr@…): * keywords: quit, exit => * owner: macports-tickets@… => stechert@… Comment: Please remember to cc the maintainer. -- Ticket URL: <http://trac.macports.org/ticket/24860#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24860: 'quit' and 'exit' do not work well for octave ----------------------------+----------------------------------------------- Reporter: qchen3@… | Owner: stechert@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: octave ----------------------------+----------------------------------------------- Comment(by glen.henshaw@…): This issue appears to be related to certain octave packages having been installed; see ticket #26340 -- Ticket URL: <https://trac.macports.org/ticket/24860#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24860: 'quit' and 'exit' do not work well for octave ----------------------------+----------------------------------------------- Reporter: qchen3@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: octave ----------------------------+----------------------------------------------- Changes (by jmr@…): * owner: stechert@… => macports-tickets@… -- Ticket URL: <https://trac.macports.org/ticket/24860#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24860: 'quit' and 'exit' do not work well for octave -----------------------+-------------------------------- Reporter: qchen3@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Resolution: | Keywords: Port: octave | -----------------------+-------------------------------- Comment (by urilabob@…): I am finding the same problem. Please find attached a complete trace of {{{ octave --debug }}} where I simply exit as soon as the prompt becomes available. I'm also attaching the core dump it generates. Any idea whether a fix is likely? It's not a deadly problem, since we can build bash scripts around it, but the problem is that it is then difficult to distinguish these spurious crashes from real ones. -- Ticket URL: <https://trac.macports.org/ticket/24860#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24860: 'quit' and 'exit' do not work well for octave -----------------------+-------------------------------- Reporter: qchen3@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Resolution: fixed | Keywords: Port: octave | -----------------------+-------------------------------- Changes (by michaelld@…): * status: new => closed * resolution: => fixed Comment: If this is still really an issue ... please do: {{{ sudo port selfupdate }}} and then try installing it again. Should be fixed with r114034. -- Ticket URL: <https://trac.macports.org/ticket/24860#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts