[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57591] Segmentation faults when running the t
From: |
Markus Mützel |
Subject: |
[Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite |
Date: |
Thu, 2 Dec 2021 14:57:05 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36 Edg/96.0.1054.41 |
Follow-up Comment #176, bug #57591 (project octave):
The whole lifetime thingy might be a red herring. And I'm not sure if I
correctly understand:
https://en.cppreference.com/w/cpp/language/lifetime
> [...] the following uses of the glvalue expression that identifies that
object are undefined, unless the object is being constructed or destructed
(separate set of rules applies):
>
> 1. Lvalue to rvalue conversion (e.g. function call to a function that takes
a value).
Perusing through the code that is being called in the tests for gmres:
https://hg.savannah.gnu.org/hgweb/octave/file/b8c7c550e86f/libinterp/corefcn/cellfun.cc#l2469
retcell = do_cellslices_nda (x.array_value (),
lb, ub, dim);
Does x.array_value () constitute a glvalue expression? Is calling a function
with that lvalue causing undefined behavior?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57591>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/