Opened 15 years ago
Closed 11 years ago
#24860 closed defect (fixed)
'quit' and 'exit' do not work well for octave
Reported by: | qchen3@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.8.2 |
Keywords: | Cc: | glen.henshaw@… | |
Port: | octave |
Description
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.
Attachments (3)
Change History (9)
comment:1 Changed 15 years ago by jmroot (Joshua Root)
Keywords: | quit exit removed |
---|---|
Owner: | changed from macports-tickets@… to stechert@… |
comment:3 Changed 14 years ago by glen.henshaw@…
This issue appears to be related to certain octave packages having been installed; see ticket #26340
comment:4 Changed 13 years ago by jmroot (Joshua Root)
Owner: | changed from stechert@… to macports-tickets@… |
---|
Changed 12 years ago by urilabob@…
Attachment: | octave-core added |
---|
comment:5 Changed 12 years ago 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.
Changed 12 years ago by urilabob@…
Attachment: | octdebug.txt added |
---|
Don't download this - dummy file - I couldn't find a way to delete
Changed 12 years ago by urilabob@…
Attachment: | octdebug.txt.gz added |
---|
gzipped trace of octave --debug run (quitting as soon as prompt appears)
comment:6 Changed 11 years ago by michaelld (Michael Dickens)
Resolution: | → fixed |
---|---|
Status: | new → closed |
If this is still really an issue ... please do:
sudo port selfupdate
and then try installing it again. Should be fixed with r114034.
Please remember to cc the maintainer.