|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write] |
Date: | Tue, 24 Apr 2018 18:30:40 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Follow-up Comment #22, bug #53733 (project octave): If this is a kernel problem, or a problem with the particular way that the address sanitizer and gdb work, would going back and trying valgrind be a solution? From what I remember, that runs the executable in simulation, which is slow, but it doesn't depend on setting magic bits on memory pages and having the kernel and CPU detect triggering conditions. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?53733> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |