Locate core dump?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Locate core dump?

Huaiyu Zhu
Hi,

I'm using octave for some heavy number-crunching and got core-dumps quite
often (after one hour computing).  My programs are quite complicated so
it's unlikely to reproduce the bug in a shorter program.

Since octave says " .... stopping myself", I'm wondering if it's possible
to show the calling sequence when it failed.  That way I may be able to
localize it in a shorter program.


error: Segmentation fault -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete
error: attempted clean up seems to have failed -- aborting...
IOT trap/Abort (core dumped)
[4]huaiyu@huaiyu:~/matlab/diffuse3$ octave
Octave, version 2.0.5 (i486-pc-linux-gnu).
Copyright (C) 1996 John W. Eaton.
This is free software with ABSOLUTELY NO WARRANTY.
For details, type `warranty'.


Huaiyu
--
Huaiyu Zhu                      Tel: 1 505 984 8800 ext 305      
Santa Fe Institute              Fax: 1 505 982 0565
1399 Hyde Park Road             mailto:[hidden email]          
Santa Fe, NM 87501              http://www.santafe.edu/~zhuh/ 
USA                             ftp://ftp.santafe.edu/pub/zhuh/  


Reply | Threaded
Open this post in threaded view
|

Locate core dump?

John W. Eaton-6
On 26-May-1998, Huaiyu Zhu <[hidden email]> wrote:

| I'm using octave for some heavy number-crunching and got core-dumps quite
| often (after one hour computing).  My programs are quite complicated so
| it's unlikely to reproduce the bug in a shorter program.
|
| Since octave says " .... stopping myself", I'm wondering if it's possible
| to show the calling sequence when it failed.  That way I may be able to
| localize it in a shorter program.
|
| error: Segmentation fault -- stopping myself...
| attempting to save variables to `octave-core'...
| save to `octave-core' complete
| error: attempted clean up seems to have failed -- aborting...
| IOT trap/Abort (core dumped)
| [4]huaiyu@huaiyu:~/matlab/diffuse3$ octave
| Octave, version 2.0.5 (i486-pc-linux-gnu).
| Copyright (C) 1996 John W. Eaton.
| This is free software with ABSOLUTELY NO WARRANTY.
| For details, type `warranty'.

Version 2.0.5 is ancient.  You should probably upgrade to 2.0.13,
which was released last week.  The newer release includes many bug
fixes and improvements over 2.0.5.  It will also produce a core file
if it happens to crash (subject to an resource limits, of course).  If
that doesn't help, you can always run Octave under the debugger.

jwe


Reply | Threaded
Open this post in threaded view
|

Re: Locate core dump?

Huaiyu Zhu
I tried to install newer versions but they require libc6 while I only got
libc5.  (Why does source code complain about version of lib, anyway?)
I haven't got the courage to migrate from RedHat 4.2 to 5.0 yet.
Does anyone know if I can simply add new libc without touching anything
else?

Here's a test with what I have now.  (I believe it would be the same for
2.0.13)

rpm -ih octave-2.0.9-2.src.rpm
failed dependencies:
        /bin/sh is needed by octave-2.0.9-2
        libstdc++.so.2.7.2 is needed by octave-2.0.9-2
        libm.so.6 is needed by octave-2.0.9-2
        libdl.so.2 is needed by octave-2.0.9-2
        libc.so.6 is needed by octave-2.0.9-2
        ld-linux.so.2 is needed by octave-2.0.9-2

--
Huaiyu Zhu                      Tel: 1 505 984 8800 ext 305      
Santa Fe Institute              Fax: 1 505 982 0565
1399 Hyde Park Road             mailto:[hidden email]          
Santa Fe, NM 87501              http://www.santafe.edu/~zhuh/ 
USA                             ftp://ftp.santafe.edu/pub/zhuh/  

On Tue, 26 May 1998, John W. Eaton wrote:
> Version 2.0.5 is ancient.  You should probably upgrade to 2.0.13,
> which was released last week.  The newer release includes many bug
> fixes and improvements over 2.0.5.  It will also produce a core file
> if it happens to crash (subject to an resource limits, of course).  If
> that doesn't help, you can always run Octave under the debugger.
>
> jwe
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Locate core dump?

John W. Eaton-6
On 27-May-1998, Huaiyu Zhu <[hidden email]> wrote:

| I tried to install newer versions but they require libc6 while I only got
| libc5.  (Why does source code complain about version of lib, anyway?)
| I haven't got the courage to migrate from RedHat 4.2 to 5.0 yet.
| Does anyone know if I can simply add new libc without touching anything
| else?
|
| Here's a test with what I have now.  (I believe it would be the same for
| 2.0.13)
|
| rpm -ih octave-2.0.9-2.src.rpm
| failed dependencies:
|         /bin/sh is needed by octave-2.0.9-2
|         libstdc++.so.2.7.2 is needed by octave-2.0.9-2
|         libm.so.6 is needed by octave-2.0.9-2
|         libdl.so.2 is needed by octave-2.0.9-2
|         libc.so.6 is needed by octave-2.0.9-2
|         ld-linux.so.2 is needed by octave-2.0.9-2

Octave can work with libc6, but the binary distribution you picked up
was linked against libc6, so you would need that.

Why don't you just build Octave from the current sources (2.0.13)?

Or, you could get the binary distribution that is available from
ftp://ftp.che.wisc.edu/pub/octave/BINARIES/2.0.13.  It is also
dynamically linked, but relative to libc5.

jwe