[Octave-bug-tracker] [bug #63300] valgrind warning from inv.cc

[Arun Giridhar]

Follow-up Comment #6, bug #63300 (project octave):

I could confirm this behavior after a lot of work:

1. Searching for gloptipolydemo, I found and read
https://homepages.laas.fr/henrion/software/gloptipoly/ then I downloaded that
software and its prerequisite sedumi, examined them and ran a demo initiated
by inst.m. This took a long time.

2. I added cout statements to inv.cc and selectively switched on or off the
initialization of info.

3. I used that information to find a MUCH simpler test case: passing a scalar
to inv() causes info to not be set:


>> inv (1)
info == 140217805074025
m ==  1
ans = 1

>> inv (i)
info == 140217805074025
m ==  (0,1)
ans =  0 - 1i

>> inv (single(1))
info == 140217805074025
m ==  1
ans = 1


4. With the initialization patch, passing a scalar causes info to be set:

>> inv (1)
info == 0
m ==  1
ans = 1

>> inv(i)
info == 0
m ==  (0,1)
ans =  0 - 1i

>> inv(single(1))
info == 0
m ==  1
ans = 1


@OP: Thank you for reporting this bug and the fix, but seriously, next time
you report a bug, please create a minimum reproducer. All you needed was one
of the scalar tests above, not an appeal to valgrind or a long GDB session
which took me far too long to replicate and confirm.

@rik & mmuetzel: Would a BIST be useful for this or is it redundant now?


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63300>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/