[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Profiling Octave
From: |
John W. Eaton |
Subject: |
Re: Profiling Octave |
Date: |
Thu, 25 Mar 2004 21:29:18 -0500 |
On 25-Mar-2004, JD Cole <address@hidden> wrote:
| Check the capitals on the text which Clinton provides and the case
| of the text coming from within octave: one is lower, the other upper. So
| that's probably not the source of the message.
Right, but the code that Przemek quoted is just there as a backup in
case the sys_siglist global variable isn't defined. So the idea is
the same, that Octave has received a SIGPROF signal. Currently there
is a handler installed for that if SIGPROF is defined, and it just
aborts with a panic message. Perhaps that is not the right action?
If it is not, then what is the correct thing to do?
jwe
- [Fwd: [Bug c++/14563] octave built under Cygwin very slow], Paul Thomas, 2004/03/25
- [Fwd: [Bug c++/14563] octave built under Cygwin very slow], John W. Eaton, 2004/03/25
- Re: [Fwd: [Bug c++/14563] octave built under Cygwin very slow], Paul Thomas, 2004/03/26
- Re: [Fwd: [Bug c++/14563] octave built under Cygwin very slow], Paul Kienzle, 2004/03/27
- Re: [Fwd: [Bug c++/14563] octave built under Cygwin very slow], Paul Thomas, 2004/03/27
- Re: [Fwd: [Bug c++/14563] octave built under Cygwin very slow], Paul Kienzle, 2004/03/27