[Octave-bug-tracker] [bug #52567] invoking octave with conflicting arguments dumps core

[Rik]

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
warning().

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:

  <http://savannah.gnu.org/bugs/?52567>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/