[Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write]

[Rik]

Follow-up Comment #44, bug #53733 (project octave):

I would also like to know the results of testing a system working with gdb
with the OP's code (comment #43).

This may be a red herring, but is this related to Spectre and Meltdown and
subsequent microcode patches by Intel?

Using 'cat /proc/cpuinfo' I find that my system is


processor       : 3
vendor_id       : GenuineIntel
cpu family      : 6
model           : 78
model name      : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
stepping        : 3
microcode       : 0xc2


It is an i7 and crashes, just as Adrian's i5 system crashes.

An additional field that I have never noticed in the output is


bugs            : cpu_meltdown spectre_v1 spectre_v2


I see that there were also reports of HW instability with the first microcode
update from Intel for Ubuntu
(https://news.softpedia.com/news/canonical-pulls-intel-s-microcode-update-from-ubuntu-repos-due-to-hardware-issue-519494.shtml).
 Maybe something is still not complely correct.


    _______________________________________________________

Reply to this item at:

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

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