Re: Crtl-C -> panic

[John W. Eaton]

On 17-Jun-2004, David Bateman <address@hidden> wrote:

| So the problem seems to be there in the current CVS, and is not due to
| older versions of the dynmaic libraries hanging around.

OK, I rebuilt with --enable-shared --disable-static (normally, I just
build static versions since it is easier for debugging) and I can
reproduce the problem.

| 8) gdb /opt/octave-2.1.57/bin/octave
|    (gdb) handle SIGINT stop print pass
|    (gdb) run
|    octave:1> Ctrl-C
|    (gdb) cont
| Continuing.
| 
| Program received signal SIGINT, Interrupt.
| 0x4158a53c in sigprocmask () from /lib/libc.so.6
| (gdb) cont
| Continuing.
| 
| Program received signal SIGABRT, Aborted.
| 0x4158a571 in kill () from /lib/libc.so.6
| (gdb) cont
| Continuing.
| panic: Aborted -- stopping myself...
| attempting to save variables to `octave-core'...
| save to `octave-core' complete
| 
| Program received signal SIGABRT, Aborted.
| 0x4158a571 in kill () from /lib/libc.so.6
| 
| Not sure what is happening here and I can't single step through the
| code in gdb to get more info....

To send a signal to a process from gdb, you can do

  (gdb) signal SIGINT

then you can step through the process.

The problem seems to be also related to building with shared
libraries, since I don't see the problem with a version that is
compiled and linked statically.

I tried commenting out the code that installs the new types and
operators for those types, but the problem remains.

Even though I can send SIGINT to Octave from gdb, I'm not sure that
will point directly to the location of the actual error.  Perhaps the
best thing to do is step backward in time with CVS and try to pinpoint
the changes that cause the problem.

| I also then tried to build octave-forge with this CVS and got no where,
| firstly the configure script failed to correctly determine some option
| (due to mkoctfile failing) and the build failed on the compile of the
| first oct-file. This seems to have something to do with the introduction
| of the int/uint types....

I expect some trouble, and will try to build octave-forge so I can see
what changes will be needed (either to Octave, or to other code) when
I get some time.

jwe