|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang) |
Date: | Wed, 28 Oct 2020 06:48:00 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36 Edg/86.0.622.51 |
Follow-up Comment #135, bug #57591 (project octave): I'm not sure if I correctly understand the backtrace. It looks like somehow an output from gdb ("Python Exception <class 'gdb.error'> There is no member named _M_dataplus.") made it into Octave's output buffer (in thread 22)... Is that expected? IIRC, there was a report in the past where Java didn't play well with gdb. Could this be one of those cases again? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57591> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |