[Top][All Lists]

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

[Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java metho

From: Rik
Subject: [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write]
Date: Sat, 28 Apr 2018 10:30:08 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

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
 Maybe something is still not complely correct.


Reply to this item at:


  Message sent via Savannah

reply via email to

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