bugGNU Octave - Bugs: bug #47568, Memory corruption in file-io.cc-tst

 
 

bug #47568: Memory corruption in file-io.cc-tst

Submitter:  None
Submitted:  Tue 29 Mar 2016 11:39:52 PM UTC
   
 
Category:  Octave Function Severity:  4 - Important
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  Invalid / Not an Octave Bug Assigned to:  None
Originator Name:  Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * dev
Operating System:  * GNU/Linux Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Thu 31 Mar 2016 10:01:49 PM UTC, comment #6: 

@Rik: Yes, John's recommendation is a good idea.
It would be helpful to include it in the Manual
(in the last entry in Section G.2?). Or, maybe better
to make the default installation directory prefix something
other than /usr/local??

However, users should be told that cleaning the install
directory may be necessary wherever they have declared it.

Michael Godfrey <godfrey>
Group Member
Thu 31 Mar 2016 09:51:35 PM UTC, comment #5: 

@Michael: In this case, I think the reporter was getting fails during 'make check' which means they were still using run-octave from the build tree.

As you say, it is also possible after several 'make install' invocations to accumulate cruft in the wider file system.  This is why jwe likes installing into a local directory that you can just delete entirely.

Rik <rik5>
Group administrator
Thu 31 Mar 2016 03:24:59 PM UTC, comment #4: 

Rik:  This is good advice, but not quite the whole story.
My recent experience of a problem continued after
removing the source octave, re-clone, bootstrap, configure,
make. The problem was with the make install which did not
(maybe still does not) update all changed files in the
install target directories.

So the added step that is needed to be in a fully clean state
is to remove the install directories.
(John figured this out.)



Michael Godfrey <godfrey>
Group Member
Thu 31 Mar 2016 03:14:29 PM UTC, comment #3: 

That's good news.  The development branch is pretty stable, for a working code repository.  But that still doesn't mean that I don't have to occasionally run 'make maintainer-clean' and 'hg stat -u -i' to find cruft that has built up.  Of course, the easiest solution is just to re-clone the repository to a new tree and run the bootstrap, configure, make cycle to make sure there is no garbage around.

Closing report.

Rik <rik5>
Group administrator
Thu 31 Mar 2016 12:34:52 PM UTC, comment #2: 

Original poster here. Problem went away after deleting all object files and doing a full rebuild.

Anonymous
Wed 30 Mar 2016 03:27:58 PM UTC, comment #1: 

Thanks for the bug report. This test works fine for me, so we need some more information to help identify the bug if there is one.

Can you identify specifically which test causes the segfault and provide a gdb backtrace? Something like the following:


$ ./run-octave -cli -g --path $srcdir/libinterp/corefcn \
               --eval "more off; test file-io.cc verbose"
... startup messages ...
(gdb) r
... tests run ...
... test crashes presumably ...
(gdb) bt


Mike Miller <mtmiller>
Group Member
Tue 29 Mar 2016 11:39:52 PM UTC, original submission:  


  libinterp/corefcn/fft2.cc-tst ............................... PASS      4/4
  libinterp/corefcn/file-io.cc-tst ............................*** glibc detected *** /tmp/build/src/.libs/lt-octave-gui: malloc(): memory corruption: 0x00002ac6e85edae0 ***


Dev version 6619945e4434.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by godfrey (Posted a comment)
  • -email is unavailable- added by rik5 (Updated the item)
  • -email is unavailable- added by mtmiller (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-03-31 rik5 StatusNeed Info Invalid / Not an Octave Bug
        Open/ClosedOpen Closed
    2016-03-30 rik5 SummaryMemory corruption in IO Memory corruption in file-io.cc-tst
    2016-03-30 mtmiller CategoryNone Octave Function
        Severity3 - Normal 4 - Important
        Item GroupNone Segfault, Bus Error, etc.
        StatusNone Need Info

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code