Hi all,
Back on Sun to GPC conversion after a year or so.
Things are going pretty well with gpc except on one point:
I run gpc on a Sparc Solaris 10 box. As soon as the cpu gets a bit loaded gpc fails with the following error:
gpc: Internal error: Alarm Clock (program gpc1) Please submit a full bug report. See URL:http://www.gnu-pascal.de/todo.html for instructions.
If I restart it it compiles some modules and stops again (I use gp). I searched for the words 'Alarm Clock' in gpc sources with no success so I cannot figure what is the problem.
Any solution, clue, idea or patch is welcome.
Regards.
Pascal Viandier
The gpc I use is: Reading specs from /usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.4/specs Configured with: ../gcc-3.4.4/configure --enable-languages=pascal Thread model: posix gpc version 20051116, based on gcc-3.4.4
Pascal Viandier wrote:
I run gpc on a Sparc Solaris 10 box. As soon as the cpu gets a bit loaded gpc fails with the following error:
gpc: Internal error: Alarm Clock (program gpc1) Please submit a full bug report. See URL:http://www.gnu-pascal.de/todo.html for instructions.
If I restart it it compiles some modules and stops again (I use gp). I searched for the words 'Alarm Clock' in gpc sources with no success so I cannot figure what is the problem.
This message is given by the shell when a program receives a SIGALRM signal and does not handle it.
Now, gpc indeed uses this signal internally when either of the "--progress-messages" or "--progress-bar" options is used. Of course, it should handle it, but there might be a bug in this code ...
Are you using these options? If so, please try without them. If it works, we know where to look.
Frank
Hi Frank,
You got it: I use --progress-messages (Through gp). If I remove the option, gpc works without being interrupted.
Regards
Pascal
Pascal Viandier wrote:
I run gpc on a Sparc Solaris 10 box. As soon as the cpu gets a bit loaded gpc fails with the following
error:
gpc: Internal error: Alarm Clock (program gpc1) Please submit a full bug report. See URL:http://www.gnu-pascal.de/todo.html for instructions.
If I restart it it compiles some modules and stops again (I use gp). I searched for the words 'Alarm Clock' in gpc sources with no
success so
I cannot figure what is the problem.
This message is given by the shell when a program receives a SIGALRM signal and does not handle it.
Now, gpc indeed uses this signal internally when either of the "--progress-messages" or "--progress-bar" options is used. Of course, it should handle it, but there might be a bug in this code ...
Are you using these options? If so, please try without them. If it works, we know where to look.
Frank
-- Frank Heckenbach, f.heckenbach@fh-soft.de, http://fjf.gnu.de/,
7977168E
GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: ACB3 79B2 7EB2 B7A7 EFDE D101 CD02 4C9D
0FE0 E5E8
-
Frank Heckenbach -
Pascal Viandier