- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Motif debugger and KDE on cygwin
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 10:05 AM
тАО09-28-2004 10:05 AM
X windows "client" applications that I start from VMS generally work except for the XWindows Motif debugger.
If I type "debug/keep" (or run a program linked with /debug) from a DECterm window then the DCL session hangs until I press
I have successfully started the VMS debugger from older versions of KDE on cygwin/xfree86 or from other window managers. I have even done this from KDE 3.1.4 on knoppix (a version of Linux that boots from CD).
Does anyone have any idea what the problem could be? I have asked on comp.os.vms as well as some other forums without any success.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 10:57 AM
тАО09-28-2004 10:57 AM
Re: Motif debugger and KDE on cygwin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 12:21 PM
тАО09-28-2004 12:21 PM
Re: Motif debugger and KDE on cygwin
28-SEP-2004 20:17:47.09 User: ppppppp Process ID: 20201B45
Node: xxxx Process name: "_FTA2:"
Process Quotas:
Account name: DEV
CPU limit: Infinite Direct I/O limit: 1024
Buffered I/O byte count quota: 298336 Buffered I/O limit: 1024
Timer queue entry quota: 255 Open file quota: 1022
Paging file quota: 582704 Subprocess quota: 30
Default page fault cluster: 64 AST quota: 1018
Enqueue quota: 5000 Shared file limit: 0
Max detached processes: 0 Max active jobs: 0
Soft CPU Affinity: off
No subprocess exists in the job.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 12:26 PM
тАО09-28-2004 12:26 PM
Re: Motif debugger and KDE on cygwin
Here's what it looks like (masking out the ip addrs):
$ tcpip show device BG5745:/full
Device_socket: bg5745 Type: STREAM
LOCAL REMOTE
Port: 49345 6000
Host: xx.xx.xx.xx xx.xx.xx.xx
Service:
RECEIVE SEND
Queued I/O 0 0
Q0LEN 0 Socket buffer bytes 0 0
QLEN 0 Socket buffer quota 61440 61440
QLIMIT 0 Total buffer alloc 0 0
TIMEO 0 Total buffer limit 491520 491520
ERROR 0 Buffer or I/O waits 1 0
OOBMARK 0 Buffer or I/O drops 0 0
I/O completed 156 127
Bytes transferred 38724 34656
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 07:18 PM
тАО09-28-2004 07:18 PM
Re: Motif debugger and KDE on cygwin
If a BG device is allocated, this means that a socket was open to yours XWindows server (cygwin/xfree86).
Have a check of yours KDE settings (xhost etc...).
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-29-2004 12:02 PM
тАО09-29-2004 12:02 PM
Re: Motif debugger and KDE on cygwin
Also, I verified that the socket exists on the PC side by running netstat.
What other kde settings should I look at? Since every other X windows application that I know of works I really don't have a clue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-29-2004 06:23 PM
тАО09-29-2004 06:23 PM
Re: Motif debugger and KDE on cygwin
First, you may use "$ SET WATCH FILE /CLASS=MAJOR" before the DEBUG/KEEP. Just before the debugger window opens, I see a series of lookups of _XMTEXT_ADDMODE_18_1.DIR/EXE/DAT and finaly a access to PTHREAD$RTL.EXE. If you also get that far (what I expect due to the absence of a error message) it would mean that the debugger actually opens the window - it is just not visible. Check if there is a DBG$DECW$DISPLAY logical pointing to nirwana.
Other than that I could only think of some IP tracing to get more information.
Edwin
P.S.
use "$ SET WATCH FILE /CLASS=NONE" to turn file watching off.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-29-2004 06:44 PM
тАО09-29-2004 06:44 PM
Re: Motif debugger and KDE on cygwin
Check also if you have a DBG$INIT logical name. This logical name points to the initialisation procedure for the debugger. Maybe there is something strange.
But if the debugger forks on other Xservers, I think that the problem is in KDE 3.1.4/cygwin/xfree86 settings.
I dont know cygwin because I use a "clean" Linux. There is a file named .xsession-errors, if such a file (or an equivalent) exists in cygwin try to examin it.
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2004 06:13 AM
тАО10-08-2004 06:13 AM
Re: Motif debugger and KDE on cygwin
> due to the absence of a error message) it
> would mean that the debugger actually
> opens the window - it is just not visible.
This is in fact the case. I.e., the window is being created, it is just not visible. I noticed that an outline of the window is created in the KDE vitual desktop icon located on the KDE task bar at the bottom of the screen. After I stop the debugger the outline disappeared. At that point I decided to ask in the help forum on the kde-cygwin project on sourceforge but I haven't gotten any replies.
So, I am still at a loss as to what is wrong here. I appreciate the help I've gotten here.
Still working on it...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2004 07:42 PM
тАО10-08-2004 07:42 PM
Re: Motif debugger and KDE on cygwin
Try to find where the window is. For this you can use the xwininfo utility.
On my linux I can do:
xwininfo -root -tree
which prints out a tree of all windows. Find the debbuger window and its id. Then do a:
xwininfo -all -id WINDOWID
this will display all the characteristics of the debugger window. Examine this output (you can post the output).
Now I am far away from a VMS system, so I cant see if the syntax on VMS is similar to Linux, but I think it is. The program is located in SYS$SYSROOT:[SYSHLP.EXAMPLES.DECW.UTILS]XWININFO.EXE
there is also a command procedure which define the symbols.
Probably the same utility exists also in cygwin.
Bojan