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

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

[Octave-bug-tracker] [bug #30478] prelinking causes octave to crash


From: John Hunt
Subject: [Octave-bug-tracker] [bug #30478] prelinking causes octave to crash
Date: Tue, 26 Oct 2010 14:53:20 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-0.3.1 Firefox/3.6.10

Follow-up Comment #25, bug #30478 (project octave):

The initial bug report is about prelinking.
By chance I found out another crash that disappears when
prelinking is off, so I found relevant to post findings here.
Please tell me if I'm wrong.

My bug requires a sequence of launching and exiting octave in two
terminals, as described in comment #8. 
Maybe it is because there are launch/exit of one instance of
octave while another is running. 
Tests run fine because there is only one terminal opened at that 
time.

Here is the output of
gdb -nx /usr/local/bin/octave core
(gdb) where
#0  0x00007f3e051df4e8 in ?? () from
/usr/local/share/GotoBLAS2/libgoto2_nehalemp-r1.13.so
#1  0x0000000000000000 in ?? ()

The problem is that the crash happens only when there are no 
debugging symbols in the executable (see comment #19), 
that's the reason for having in the backtrace those 
"in ?? ()", isn't it ?



    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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