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

 
 

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

Submitted by:  None
Submitted on:  Tue 29 Mar 2016 11:39:52 PM UTC  
 
Category: Octave FunctionSeverity: 4 - Important
Priority: 5 - NormalItem Group: Segfault, Bus Error, etc.
Status: InvalidAssigned to: None
Originator Name: Originator Email: -unavailable-
Open/Closed: ClosedRelease: dev
Operating System: GNU/Linux

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission 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>
Project 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>
Project 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>
Project 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>
Project 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:

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

Dev version 6619945e4434.

Anonymous

 

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

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

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

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 7 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 31 Mar 2016 03:14:29 PM UTCrik5StatusNeed Info=>Invalid
      Open/ClosedOpen=>Closed
    Wed 30 Mar 2016 03:32:10 PM UTCrik5SummaryMemory corruption in IO=>Memory corruption in file-io.cc-tst
    Wed 30 Mar 2016 03:27:58 PM UTCmtmillerCategoryNone=>Octave Function
      Severity3 - Normal=>4 - Important
      Item GroupNone=>Segfault, Bus Error, etc.
      StatusNone=>Need Info

    Back to the top


    Powered by Savane 3.1-cleanup1