From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zoltan Kemenczy To: "'cygwin@sourceware.cygnus.com'" Subject: Ptolemy 0.7.1 on NTsp3 - pigiRpc Aborts Often Date: Wed, 18 Aug 1999 07:35:00 -0000 Message-id: X-SW-Source: 1999-08/msg00368.html Hi Everyone, I have compiled Ptolemy 0.7.1 (PtolemyClassic http://ptolemy.eecs.berkeley.edu/ ) on NTsp3 with: Cygwin B20.1+Win95 make/fork/fault patch and egcs-1.1.2. (For Ptolemy Hackers: I found that the Win95 make/fork/fault patch fixes the problem with % characters in pathnames. I am using the prebuilt X11R6.4 binaries and Exceed 6.1 for X-server. I have also removed the -DPT_NO_TIMERS from LOCALCCFLAGS config-nt4.mk for pigiRpc to run at normal speeds and haven't found any demos that aren't working yet, including the Tk demos under SDF). Now the problem: Whenever there seems to be some kind of problem in the simulation (i.e. a port is not connected in some deeper-buried galaxy...), instead of completing the error messages and highlighting the associated icons with red, pigiRpc exits with the following error: Ptolemy failed to receive response from Vem! RPC Error: application: ../../../../src/octtools/Xpackages/rpc/rpc.c (line 79): RPCReceiveLong(&dummy, stream): Interrupted system call /users/ptolemy/bin.nt4/pigiRpc: fatal error detected by rpc (code -1): RPC Error: application: ../../../../src/octtools/Xpackages/rpc/rpc.c (line 79): RPCReceiveLong(&dummy, stream) Vem RPC: client has failed. I suspect this is some kind of problem with the cygwin fread / signal handling / masking. In the Cygwin User's Guide unde the Signals section they talk about some of this stuff, so I'm not sure if the "Interrupted system call" message is a sign of a hole in cygwin or is Ptolemy not compliant with the current cygwin-level of POSIX implementation? Has anyone seen this problem before, any ideas for a fix, or what to try to narrow it down? When I run this in pigi -debug mode and set breakpoints in rpc.c to catch the error, the gdb backtrace is about 70 frames deep... Thank you, Zoltan Kemenczy, zkemenczy@rim.net DSP Software Engineering Research in Motion Limited Waterloo, Canada N2L 3W8 www.rim.net -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zoltan Kemenczy To: "'cygwin@sourceware.cygnus.com'" Subject: Ptolemy 0.7.1 on NTsp3 - pigiRpc Aborts Often Date: Tue, 31 Aug 1999 23:49:00 -0000 Message-ID: X-SW-Source: 1999-08n/msg00368.html Message-ID: <19990831234900.YNGWhE_uPHajqA0pw0PRL5JH8K8OPRH2HLBU9emFyAc@z> Hi Everyone, I have compiled Ptolemy 0.7.1 (PtolemyClassic http://ptolemy.eecs.berkeley.edu/ ) on NTsp3 with: Cygwin B20.1+Win95 make/fork/fault patch and egcs-1.1.2. (For Ptolemy Hackers: I found that the Win95 make/fork/fault patch fixes the problem with % characters in pathnames. I am using the prebuilt X11R6.4 binaries and Exceed 6.1 for X-server. I have also removed the -DPT_NO_TIMERS from LOCALCCFLAGS config-nt4.mk for pigiRpc to run at normal speeds and haven't found any demos that aren't working yet, including the Tk demos under SDF). Now the problem: Whenever there seems to be some kind of problem in the simulation (i.e. a port is not connected in some deeper-buried galaxy...), instead of completing the error messages and highlighting the associated icons with red, pigiRpc exits with the following error: Ptolemy failed to receive response from Vem! RPC Error: application: ../../../../src/octtools/Xpackages/rpc/rpc.c (line 79): RPCReceiveLong(&dummy, stream): Interrupted system call /users/ptolemy/bin.nt4/pigiRpc: fatal error detected by rpc (code -1): RPC Error: application: ../../../../src/octtools/Xpackages/rpc/rpc.c (line 79): RPCReceiveLong(&dummy, stream) Vem RPC: client has failed. I suspect this is some kind of problem with the cygwin fread / signal handling / masking. In the Cygwin User's Guide unde the Signals section they talk about some of this stuff, so I'm not sure if the "Interrupted system call" message is a sign of a hole in cygwin or is Ptolemy not compliant with the current cygwin-level of POSIX implementation? Has anyone seen this problem before, any ideas for a fix, or what to try to narrow it down? When I run this in pigi -debug mode and set breakpoints in rpc.c to catch the error, the gdb backtrace is about 70 frames deep... Thank you, Zoltan Kemenczy, zkemenczy@rim.net DSP Software Engineering Research in Motion Limited Waterloo, Canada N2L 3W8 www.rim.net -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com