solbox% setenv DISPLAY linuxbox:0
solbox% olitprog
Segmentation fault (core dumped)
Any ideas?
Griff
Try running pstack on the core file; maybe something will suggest itself.
Maybe it's something goofy, like certain fonts not being available
(especially the open look cursor fonts, which might be a rather
basic assumption; I do see a wildcard for them in a "strings" on
libXol.so.3).
Try making sure that the X font server is enabled on the Solaris
system, and including a reference to that font server in the font
path of the linux box.
--
mailto:rlh...@smart.net http://www.smart.net/~rlhamil
Lasik/PRK theme music:
"In the Hall of the Mountain King", from "Peer Gynt"
I tried that - it is suggestive:
7fa5c7f8 _OlCanonicalKeysym (29d00, ffcd, 0, 0, 7fb25904, 59) + 78
7fa5bd0c StringToKeyDefOrBtnDef (29d00, 1, 89398, ffbebbb4, 7fb25904,
8939e) + 13c
7fa5d1d8 _OlStringToOlKeyDef (29d00, ffbebd88, ffbebcb0, 7fb391dc,
7fb391c8, 7fb25904) + c0
7f9a6418 CallConverter (ffbebdac, 85d98, 0, 7f9f2000, ffbebd90,
ffbebd88) + 4f0
7f9a5b3c _XtConvert (28ea0, 0, ffbebd90, 252, ffbebd88, ffbebdac) +
160
7f9a5524 GetResources (7f9f2000, ffbebdac, 8ae38, 0, ffbecbc0, 252) +
b94
7f9ae048 XtGetApplicationResources (89788, 28ea0, ffbecf5c, 38,
ffbed024, 0) + 1b0
7fa5be8c UpdateIEDB (8ae38, 97010, 7fb25904, 979c0, 8a76e, 8ae38) +
118
7fa75740 OlCreateInputEventDB (8a750, 97010, 38, 980cc, 38, 7fb2e0f4)
+ 464
7fa7758c _OlInitDynamicHandler (7fb3e320, 7fb25904, 8a750, 0, 22318,
7fa73424) + 14c
7fa7345c DisplayShellInitialize (ffbedf00, 8ae38, 7fb25904, ffbede34,
7fb35004, 7fa76484) + 50
7f9a6cbc CallInitialize (7f9f5c88, 7f9f5c84, 8ae38, 8ae00, 7fb353f8,
7fa7340c) + d0
7f9a2fc4 xtCreate (0, 6, 8ae38, 138, 0, 8ae00) + 260
7f9a2d2c _XtAppCreateShell (25888, 0, 0, 7fb353f8, 8ae00, 6) + bc
7f9a2c2c XtAppCreateShell (25888, 0, 7fb353f8, 7fb353f8, 8ae00, 6) +
88
7fa4fdc0 OlCreateDisplayShell (7fb25904, 886e8, 3, 3, 8ae00, 0) + 294
7fa4f2b4 Initialize (8ad60, 886e8, ffbee708, ffbee57c, 95408,
7fb25904) + 3c
7f9a6cbc CallInitialize (7f9f5c88, 7f9f5c84, 886e8, 95408, 7fb38400,
7fa4f278) + d0
7f9a6c68 CallInitialize (7f9f5c88, 7f9f5c84, 886e8, 95408, 7f9f6908,
3) + 7c
7f9a6c68 CallInitialize (7f9f5c88, 7f9f5c84, 886e8, 95408, 7f9f69f0,
3) + 7c
7f9a2fc4 xtCreate (0, 3, 886e8, 148, 124b8, 95408) + 260
7f9a2d2c _XtAppCreateShell (0, 124b8, 124b8, 7f9f69f0, 95408, 3) + bc
7f9a2c2c XtAppCreateShell (0, 0, 7f9f69f0, 7f9f69f0, 95408, 3) + 88
7f99ee54 XtOpenApplication (29d00, 95408, 3, 0, 0, ffbeec5c) + 11c
7f99ed18 XtAppInitialize (ffbeec5c, 124b8, 0, 0, ffbeed74, ffbeed94) +
4c
7fab7400 OlMidInitialize (124b4, 124b8, 0, 0, ffbeed74, ffbeed94) + 24
7fab6ea0 OlInitialize (124b4, 124b8, 0, 0, ffbeed74, ffbeed94) + 88
000113b4 main (3, ffbeed94, ffbeeda4, 22800, 0, 0) + cc
000112d0 _start (0, 0, 0, 0, 0, 0) + 108
So perhaps it's something have to do with keyboard setup? (I presume
that the pstack output lists the last thing that happened on top)
Perhaps OLIT can't cope with a PC keyboard, though surely it does all
the time in the Solaris X86 world.
> Maybe it's something goofy, like certain fonts not being available
> (especially the open look cursor fonts, which might be a rather
> basic assumption; I do see a wildcard for them in a "strings" on
> libXol.so.3).
>
> Try making sure that the X font server is enabled on the Solaris
> system, and including a reference to that font server in the font
> path of the linux box.
Good idea, but it wasn't the fonts.
With XView apps running on Solaris but DISPLAYed on Linux, fonts
are indeed the issue. I got around it by copying fontdirs from
the Sun to the Linux machine, and configuring the Linux fontserver
to use them. Just adding the Solaris fontserver via xset fp+ probably
would have been a lot simpler test. :)
Thanks!
Griff
> In article <10ska49...@corp.supernews.com>,
> Griff Miller <griff....@positron.com> writes:
>> Does anyone know how to get a program that uses OLIT
>> widgets to display on Linux?
>>
>> solbox% setenv DISPLAY linuxbox:0
>> solbox% olitprog
>> Segmentation fault (core dumped)
>>
>> Any ideas?
>
> Try running pstack on the core file; maybe something will suggest itself.
>
> Maybe it's something goofy, like certain fonts not being available
> (especially the open look cursor fonts, which might be a rather
> basic assumption; I do see a wildcard for them in a "strings" on
> libXol.so.3).
>
> Try making sure that the X font server is enabled on the Solaris
> system, and including a reference to that font server in the font
> path of the linux box.
I got kind of sidetracked from this, but finally took another look at it
today. The stack that I posted previously indicated that it dies in
OlCanonicalKeysym, which is apparently some internal OLIT function
that tries to make some sort of mapping of keysyms a la <X11/keysymdef.h> .
The 2nd arg to OlCanonicalKeysym seems to give the keysym that it's
looking for. Anyway, xmodmap -pk indicated that I didn't have these
keysyms mapped to anything on my Linux display, so I did them
manually:
xmodmap -e "keysym F2 = L2"
xmodmap -e "keysym F3 = L3"
xmodmap -e "keysym F4 = L4"
xmodmap -e "keysym F5 = L5"
xmodmap -e "keysym F6 = L6"
xmodmap -e "keysym F7 = L7"
xmodmap -e "keysym F8 = L8"
xmodmap -e "keysym F9 = L9"
xmodmap -e "keysym F10 = L10"
xmodmap -e "keysym KP_7 = R7"
xmodmap -e "keysym KP_9 = R9"
xmodmap -e "keysym KP_1 = R13"
xmodmap -e "keysym KP_3 = R15"
That seems to have done the trick. I can display OLIT apps on a
Linux X server now.
The above script probably needs some work to prevent problems in
other non-OLIT apps - for example I noticed that I now get a warning
when I try to run xcleardiff about keysyms. But at least I'm on the
right track!
Thanks!
Griff