[Octave-bug-tracker] [bug #59228] embedded.cc example crashes with segfault

[Markus Mützel]

Follow-up Comment #16, bug #59228 (project octave):

I used the report Dmitri posted on the mailing list a few weeks back:
https://lists.gnu.org/archive/html/octave-maintainers/2020-10/msg00026.html

I believe there were instructions somewhere on how to create such a report
(maybe on the wiki?). IIRC, I was able to reproduce those steps a while back.
But I can't find the instructions right now. Maybe comment #0 in bug #58569
might help...

Tbh, I didn't anticipate that that change would actually fix anything. I
haven't looked in detail at how we are counting references. But there are a
lot of issues in the analysis report related to the reference counter (double
free, double delete, ...). The majority (or all?) of those are probably false
positives. (But tbh again, I can't really judge.)
In that particular case, I just figured that the additional checks wouldn't
hurt much and it was quite clear what the analysis was complaining about.
Other issues in that report aren't that clear to me...

There are quite a few reported dead assignments that might also be easy fixes.
But those can't cause segfaults afaict...

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59228>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/