[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #52567] invoking octave with conflicting argum

From: Rik
Subject: [Octave-bug-tracker] [bug #52567] invoking octave with conflicting arguments dumps core
Date: Fri, 1 Dec 2017 00:14:42 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Update of bug #52567 (project octave):

                Category:                    None => Interpreter            
                  Status:                    None => Patch Submitted        


Follow-up Comment #2:

The interpreter should never segfault, even for erroneous input.

I have some guesses as to why this is happening, but the simplest thing to do
is probably to print the message directly to stderr rather than going through

And looking through octave.cc, this is not the only place where warning() is
used.  I tried combining --eval CODE with specifying an m-file to run and got
a slightly different core dump.

./run-octave -f --eval 'disp (pi);' tst_plotyy.m 
warning: --eval "CODE" and script file are mutually exclusive options
octave exited with signal 6

Try the attached patch 52567.cset.  It works for me.

(file #42541)

Additional Item Attachment:

File name: 52567.cset                     Size:1 KB


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]