On Tuesday 23 August 2005 18:57, Sergey Plis wrote: > Hi! > > I have compiled bigforth on a cluster where each node has 2 Intel(R) > Xeon (TM) CPU 2.80GHz. > > I am having following problems: > > 1. xbigforth does not start with message "Couldn't open input method"
Look at the shell variable XMODIFIERS. If it's set to some unreasonable
value, opening the input method will fail (or if the input handler has
crashed ;-). Usually, unsetting XMODIFIERS cures all possible problems.
> 2. bigforth starts but if I put something on the floating point stack
> and try to display it eather with f. or with f.s bigforth spends
> forever inside those words without printing anything and just eating
> cycles
That's really weird. Try to start bigforth with gdb bigforth, and ^C it
when it hangs, and check with x/i $pc (and several returns) where it
fails.
% gdb bigforth
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "x86_64-suse-linux"...(no debugging symbols
found)
Using host libthread_db library "/lib64/tls/libthread_db.so.1".
(gdb) r
Starting program: /home/bernd/proj/bigforth/bigforth
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
ANS bigFORTH 386-Linux rev. 2.1.1
: test begin again ; ok
test
Program received signal SIGINT, Interrupt.
0x10021a68 in ?? ()
(gdb) x/i $pc
0x10021a68: jmp 0x10021a68
(gdb)
0x10021a6d: xchg %esi,%esp
(gdb)
0x10021a6f: ret
(gdb) display/i $pc
1: x/i $pc 0x10021a68: jmp 0x10021a68
(gdb) si
0x10021a68 in ?? ()
1: x/i $pc 0x10021a68: jmp 0x10021a68
(gdb) si
0x10021a68 in ?? ()
1: x/i $pc 0x10021a68: jmp 0x10021a68
(gdb) si
0x10021a68 in ?? ()
1: x/i $pc 0x10021a68: jmp 0x10021a68
(gdb)
In this case, the reason for the program to hang is obvious, but this
gdb session shows you how to find out more.
> I work with this cluster through ssh -X and through vnc. Behaviour
> does not change.
xbigforth works definitely fine through ssh -X, just tried it.
If you have ttf fonts unavailable (quite common on a server), xbigforth
or rather xft will try to do its best not to crash - but output rubbish
(empty rectangles) instead.
What we can definitely exclude is the SMP part of this configuration.
I've a dual Opteron system (the file-server at work), and bigFORTH
works fine there.
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
pgprOyZi1BC6j.pgp
Description: PGP signature
