octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #47837] Segmentation fault with missing warnin


From: Rik
Subject: [Octave-bug-tracker] [bug #47837] Segmentation fault with missing warning state "all"
Date: Tue, 03 May 2016 16:04:40 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0

Update of bug #47837 (project octave):

                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #2:

Confirmed.  This "works" with version 4.0.2 where it only produces an error
message.  But on the development branch it hits an assert statement which
causes a panic.

The default branch code in the function warning_query in error.cc looks like
this:


  if (found)
    {
      retval.assign ("identifier", id);
      retval.assign ("state", val);
    }
  else
    error ("warning: unable to find default warning state!");

  return retval;


On the development branch the code now looks like this:


  // The warning state "all" is always supposed to remain in the list,
  // so we should always find a state, either explicitly or by using the
  // state for "all".

  assert (found);

  retval.assign ("identifier", id);
  retval.assign ("state", val);


According to 'hg blame' the cset that made the change was 20535:b70cc4bd8109
by jwe.  I've added him to the CC list for this bug.  The easiest solution
would be to revert the code, but it's also true that one shouldn't be able to
get rid of the 'all' identifier.  That just sounds like a harder fix.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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