[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java metho
From: |
Adrian |
Subject: |
[Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write] |
Date: |
Fri, 27 Apr 2018 17:47:59 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #37, bug #53733 (project octave):
This is really puzzling, as the small program from comment #12 works well with
or without gdb on my current system (octave 4.2.2, kernel 4.9 or 4.15), as I
reported in comment #28. I even just upgraded gdb from 7.12-6 to 7.12-6-b1 to
match the version of yours (this also draws in libpython3.6-minimal,
libpython3.6-stdlib and libpython3.6), but still it does not produce any error
and exits normally.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53733>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], (continued)
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Dmitri A. Sergatskov, 2018/04/25
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], John W. Eaton, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Rik, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], John W. Eaton, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], John W. Eaton, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write],
Adrian <=
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Rik, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Dmitri A. Sergatskov, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Dmitri A. Sergatskov, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/28
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Rik, 2018/04/28
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Dmitri A. Sergatskov, 2018/04/28
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Dmitri A. Sergatskov, 2018/04/28
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Dmitri A. Sergatskov, 2018/04/28