jensen@gt-eedsp.UUCP (P. Allen Jensen) (09/08/88)
I have two problems that I have not been able to solve (all running X11R2):
1) I have a Dialog Widget with a command button for getting a file name
from the user. The server is a uVax QVSS and the Client is a Multiflow
Trace. The Client is running BSD4.3 and the Server is running Ultrix 1.1
There are other command buttons and scrollbars used by the program.
Everything is fine until I try to type the filename into the dialogWidget
input area. The program then hangs in XtWaitForReadable.
The same client compiled on a Vax 11/780 running BSD4.2 works ok.
The Dialog Widget is in a boxWidget that is in a toplevelShell.
The toplevelShell is created AFTER starting XtMainLoop (its activated
from a callback to a commandButton).
2) When Thumbing (pressing middle button) a scrollbar widget,
a core dump occurs. If I just click the middle button, the thumb
does what it is supposed to do. If I hold down the middle button
to slide the thumb, then I get a core-dump. There are callback
procedures set up for both the Scrolled and Thumbed events.
The Server is a uVax QVSS running Ultrix 1.1 and the Client is
a Vax 11/780 running BSD4.2
--
P. Allen Jensen
Georgia Tech, School of Electrical Engineering, Atlanta, GA 30332-0250
USENET: ...!{allegra,hplabs,ihnp4,ulysses}!gatech!gt-eedsp!jensen
INTERNET: jensen@gteedsp.gatech.eduswick@ATHENA.MIT.EDU (Ralph R. Swick) (09/08/88)
Date: 7 Sep 88 18:09:02 GMT
From: gt-eedsp!jensen@gatech.edu (P. Allen Jensen)
Everything is fine until I try to type the filename into the dialogWidget
input area. The program then hangs in XtWaitForReadable.
? There's no such routine in my copy of the R2 libraries
2) When Thumbing (pressing middle button) a scrollbar widget,
a core dump occurs.
There _is_ a portability botch in the interfaces defined by Scrollbar for
it's thumb callbacks, but they do work on your particular machine.
Check your callback procedures, and provide a stack trace if possible.jensen@gt-eedsp.UUCP (P. Allen Jensen) (09/09/88)
In article <433@gt-eedsp.UUCP>, jensen@gt-eedsp.UUCP (P. Allen Jensen) writes: > ........... > 1) I have a Dialog Widget with a command button for getting a file name > from the user. The server is a uVax QVSS and the Client is a Multiflow > Trace. The Client is running BSD4.3 and the Server is running Ultrix 1.1 > > There are other command buttons and scrollbars used by the program. > Everything is fine until I try to type the filename into the dialogWidget > input area. The program then hangs in XtWaitForReadable. Sorry, that should have been XWaitForReadable - The full traceback is: (dbx) where >select(4, -27980, 0, 0, 0) at 0x11c324 _XWaitForReadable(1376256) at 0xecd48 _XRead(1376256, 1380352, 1328) at 0xdd284 XGetKeyboardMapping(1376256, 86, 166, 1376424) at 0xeec0c $libX$XKeyBind.Initialize(1376256) at 0xb75b4 XLookupKeysym(-25884, 0) at 0xb6f40 XEventToTMEvent(-25884, -27248) at 0x8b5f0 _XtTranslateEvent(1369600, 1369676, -25884) at 0x8b9f4 DispatchEvent(-25884, 1369600, 1) at 0x5533c XtDispatchEvent(-25884) at 0x5638c XtMainLoop() at 0x58180 main(argc = 1, argv = 0xffff9c88), line 31 in "xsignal.c" mlsetup(-25468) at 0x69c call_mlsetup() at 0x184 (dbx) As you can see - it is stuck in the select. That is why I think it may be a BSD4.3 vs Ultrix 1.1 incompatability in the network protocols. Any ideas anyone ? -- P. Allen Jensen Georgia Tech, School of Electrical Engineering, Atlanta, GA 30332-0250 USENET: ...!{allegra,hplabs,ihnp4,ulysses}!gatech!gt-eedsp!jensen INTERNET: jensen@gteedsp.gatech.edu