octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #37234] IDE hangs upon "exit" when in debug mo


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #37234] IDE hangs upon "exit" when in debug mode.
Date: Sat, 13 Oct 2012 03:40:59 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.6.24-1.fc14 Firefox/3.6.24

Follow-up Comment #4, bug #37234 (project octave):

I suggest leaving this bug open, or perhaps create a new one that isn't
specific to "when in debug mode".  It's actually more general than that.  I'm
pretty sure there is a bad memory/pointer bug in there somewhere.  I've left
the stderr un-redirected and when I close the application get a very long
string of errors and violations that ends as:

7feedd524000-7feedd7bf000 r-xp 00000000 fd:00 74423                     
/usr/lib64/libqscintilla2.so.8.0.2
7feedd7bf000-7feedd9bf000 ---p 0029b000 fd:00 74423                     
/usr/lib64/libqscintilla2.so.8.0.2
7feedd9bf000-7feedd9cd000 rw-p 0029b000 fd:00 74423                     
/usr/lib64/libqscintilla2.so.8.0.2
7feedd9cd000-7feedd9cf000 rw-p 00000000 00:00 0 
7feedd9cf000-7feedd9d0000 r--s 00000000 fd:00 57108                     
/var/cache/fontconfig/3c3fb04d32a5211b073874b125d29701-le64.cache-3
7feedd9d0000-7feedd9d1000 r--s 00000000 fd:00 57107                     
/var/cache/fontconfig/e61abf8156cc476151baa07d67337cae-le64.cache-3
7feedd9d1000-7feedd9d5000 r--s 00000000 fd:00 57106                     
/var/cache/fontconfig/b67b32625a2bb51b023d3814a918f351-le64.cache-3
7feedd9d5000-7feedd9d7000 r--s 00000000 fd:00 57105                     
/var/cache/fontconfig/d3379abda271c4acd2ad0c01f565d0b0-le64.cache-3
7feedd9d7000-7feedd9d8000 r--s 00000000 fd:00 57104                     
/var/cache/fontconfig/b4d0b56f766d89640448751fcd18ec1e-le64.cache-3
7feedd9d8000-7feedd9e1000 r--s 00000000 fd:00 57103                     
/var/cache/fontconfig/12b26b760a24f8b4feb03ad48a333a72-le64.cache-3
7feedd9e1000-7feedd9e8000 r--s 00000000 fd:00 72179                     
/usr/lib64/gconv/gconv-modules.cache
7feedd9e8000-7feede9a0000 r-xp 00000000 fd:00 13369622                  
/usr/local/src/octave/octave-gui_no_casts2/build-gui-2/libinterp/.libs/liboctinterp.so.1.0.1
7feede9a0000-7feedeba0000 ---p 00fb8000 fd:00 13369622                  
/usr/local/src/octave/octave-gui_no_casts2/build-gui-2/libinterp/.libs/liboctinterp.so.1.0.1
7feedeba0000-7feedebfb000 rw-p 00fb8000 fd:00 13369622                  
/usr/local/src/octave/octave-gui_no_casts2/build-gui-2/libinterp/.libs/liboctinterp.so.1.0.1
7feedebfb000-7feedec04000 rw-p 00000000 00:00 0 
7feedec04000-7feeded03000 r-xp 00000000 fd:00 13369789                  
/usr/local/src/octave/octave-gui_no_casts2/build-gui-2/libgui/.libs/liboctgui.so.0.0.0
7feeded03000-7feedef03000 ---p 000ff000 fd:00 13369789                  
/usr/local/src/octave/octave-gui_no_casts2/build-gui-2/libgui/.libs/liboctgui.so.0.0.0
7feedef03000-7feedef0c000 rw-p 000ff000 fd:00 13369789                  
/usr/local/src/octave/octave-gui_no_casts2/build-gui-2/libgui/.libs/liboctgui.so.0.0.0
7feedef0c000-7feedef12000 rw-p 00000000 00:00 0 
7fffc0f76000-7fffc0f99000 rw-p 00000000 00:00 0                         
[stack]
7fffc0fff000-7fffc1000000 r-xp 00000000 00:00 0                         
[vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                 
[vsyscall]
panic: Aborted -- stopping myself...
attempting to save variables to 'octave-workspace'...
panic: attempted clean up apparently failed -- aborting...

There is a patch at

http://savannah.gnu.org/patch/?7857

that cleans up a large amount of code, properly deleting objects so that
memory isn't leaked, fixing a number of bugs.  It only addresses startup and
editor behavior.  Addressing these other bugs should follow that.

My guess about this particular bug is that an object isn't being deleted
properly.  (Whenever there is a "new" used, the first thing the programmer
should do is find the proper spot for its associated "delete".)  Cleanup is
often very important in object oriented programming.

The shadow variables I've found to be innocuous, but they should be cleaned
up.  Typically it is where "parent" is used as the input to a constructor, but
the variable "parent" is already in the class.  Just replace constructor
argument "parent" with "p", etc.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?37234>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]