- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: 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
тАО10-08-2004 11:58 PM
тАО10-08-2004 11:58 PM
Re: Motif debugger and KDE on cygwin
Another idea, check if you have the file DECW$USER_DEFAULTS:VMSDEBUG.DAT. If you have this file try to rename before invoking the dbugger. In this file are the XWindows settings for the debugger, maybe some setting is misconfigured. You may look in the file, it is a normal text file.
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2004 02:00 AM
тАО10-11-2004 02:00 AM
Re: Motif debugger and KDE on cygwin
xwininfo: Window id: 0x1c00053 "OpenVMS Debug64"
Root window id: 0x3a (the root window) (has no name)
Parent window id: 0x3a (the root window) (has no name)
1 child:
0x1c00054 (has no name): () 620x700+0+0 +11+30
2 children:
0x1c00082 (has no name): () 620x35+0+0 +11+30
0x1c00055 (has no name): () 620x665+0+35 +11+65
1 child:
0x1c00056 (has no name): () 620x665+0+0 +11+65
6 children:
0x1c00081 (has no name): () 50x8+550+661 +561+726
0x1c00080 (has no name): () 50x8+550+462 +561+527
0x1c0007f (has no name): () 50x8+550+508 +561+573
0x1c00077 (has no name): () 612x145+3+515 +14+580
1 child:
0x1c00078 (has no name): () 612x145+0+0 +15+581
3 children:
0x1c0007d (has no name): () 595x13+0+132 +15+713
0x1c0007c (has no name): () 13x128+599+0 +614+581
0x1c00079 (has no name): () 595x128+0+0 +15+581
0x1c00074 (has no name): () 614x40+3+469 +14+534
1 child:
0x1c00075 (has no name): () 610x36+2+2 +16+536
7 children:
0x1c00093 (has no name): () 46x32+352+2 +368+538
0x1c00090 (has no name): () 86x32+265+2 +281+538
0x1c0008f (has no name): () 55x32+209+2 +225+538
0x1c0008e (has no name): () 35x32+173+2 +189+538
0x1c0008d (has no name): () 61x32+111+2 +127+538
0x1c0008c (has no name): () 56x32+54+2 +70+538
0x1c00076 (has no name): () 53x32+0+2 +16+538
0x1c00058 (has no name): () 614x460+3+3 +14+68
4 children:
0x1c0006e (has no name): () 113x419+0+0 +14+68
2 children:
0x1c00072 (has no name): () 33x416+0+3 +14+71
28 children:
0x1c000b3 (has no name): () 14x14+16+373 +30+444
0x1c000b2 (has no name): () 14x14+16+359 +30+430
0x1c000b1 (has no name): () 14x14+16+345 +30+416
0x1c000b0 (has no name): () 14x14+16+331 +30+402
0x1c000af (has no name): () 14x14+16+317 +30+388
0x1c000ae (has no name): () 14x14+16+303 +30+374
0x1c000ad (has no name): () 14x14+16+289 +30+360
0x1c000ac (has no name): () 14x14+16+275 +30+346
0x1c000ab (has no name): () 14x14+16+261 +30+332
0x1c000aa (has no name): () 14x14+16+247 +30+318
0x1c000a9 (has no name): () 14x14+16+233 +30+304
0x1c000a8 (has no name): () 14x14+16+219 +30+290
0x1c000a7 (has no name): () 14x14+16+205 +30+276
0x1c000a6 (has no name): () 14x14+16+191 +30+262
0x1c000a5 (has no name): () 14x14+16+177 +30+248
0x1c000a4 (has no name): () 14x14+16+163 +30+234
0x1c000a3 (has no name): () 14x14+16+149 +30+220
0x1c000a2 (has no name): () 14x14+16+135 +30+206
0x1c000a1 (has no name): () 14x14+16+121 +30+192
0x1c000a0 (has no name): () 14x14+16+107 +30+178
0x1c0009f (has no name): () 14x14+16+93 +30+164
0x1c0009e (has no name): () 14x14+16+79 +30+150
0x1c0009d (has no name): () 14x14+16+65 +30+136
0x1c0009c (has no name): () 14x14+16+51 +30+122
0x1c0009b (has no name): () 14x14+16+37 +30+108
0x1c0009a (has no name): () 14x14+16+23 +30+94
0x1c0008a (has no name): () 14x14+16+9 +30+80
0x1c00073 (has no name): () 14x14+1+1 +15+72
0x1c0006f (has no name): () 80x419+33+0 +47+68
0x1c0006d (has no name): () 15x403+599+0 +613+68
0x1c00068 (has no name): () 614x39+0+421 +14+489
4 children:
0x1c0006c (has no name): () 178x29+434+5 +448+494
0x1c0006b (has no name): () 30x35+2+2 +16+491
0x1c0006a (has no name): () 46x9+33+22 +47+511
0x1c00069 (has no name): () 60x15+32+4 +46+493
0x1c00059 (has no name): () 486x419+113+0 +127+68
3 children:
0x1c00067 (has no name): () 100x62+150+70 +277+138
0x1c00066 (has no name): () 150x45+125+20 +252+88
0x1c0005a (has no name): () 486x419+0+0 +127+68
2 children:
0x1c00065 (has no name): () 486x13+0+406 +127+474
0x1c0005b (has no name): () 486x402+0+0 +127+68
Absolute upper-left X: 11
Absolute upper-left Y: 30
Relative upper-left X: 11
Relative upper-left Y: 30
Width: 620
Height: 700
Depth: 24
Visual Class: TrueColor
Border width: 0
Class: InputOutput
Colormap: 0x20 (installed)
Bit Gravity State: ForgetGravity
Window Gravity State: NorthWestGravity
Backing Store State: NotUseful
Save Under State: no
Map State: IsUnMapped
Override Redirect State: no
Corners: +11+30 -393+30 -393-38 +11-38
-geometry 620x700+11+30
Bit gravity: ForgetGravity
Window gravity: NorthWestGravity
Backing-store hint: NotUseful
Backing-planes to be preserved: 0xffffffff
Backing pixel: 0
Save-unders: No
Someone wants these events:
KeyPress
KeyRelease
EnterWindow
LeaveWindow
Exposure
StructureNotify
FocusChange
PropertyChange
ColormapChange
Do not propagate these events:
Override redirection?: No
Window manager hints:
Client accepts input or input focus: Yes
Initial state is Don't Care State
Normal window size hints:
Program supplied location: 11, 30
Program supplied size: 620 by 700
Program supplied minimum size: 300 by 112
Program supplied window gravity: NorthWestGravity
No zoom window size hints defined
No window shape defined
No border shape defined
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2004 02:06 AM
тАО10-11-2004 02:06 AM
Re: Motif debugger and KDE on cygwin
%DIRECT-W-NOFILES, no files found
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2004 03:19 AM
тАО10-11-2004 03:19 AM
Re: Motif debugger and KDE on cygwin
Strange, from xwininfo the debugger is on the screen. Is the debugger also visible in the windows list of the KDE task bar? If so, try to right click on the button in the window list and try to move it with move.
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2004 05:14 AM
тАО10-11-2004 05:14 AM
Re: Motif debugger and KDE on cygwin
> windows list of the KDE task bar?
No, it isn't on the task bar nor is it accessible via "alt-tab" (which I have remapped).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2004 09:35 AM
тАО10-11-2004 09:35 AM
SolutionIn my previous post I say that the debugger window should be on the screen. There is a line which says a little different:
Map State: IsUnMapped
Searching the documentation I could not find when the window is in this state. Some references are on a iconified window, but maybe the window is also in this state before calling XMapWindow.
Check in which state is the debugger process. Also try to change to another virtual desktop and then return to yours current virtual desktop.
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2004 10:59 AM
тАО10-11-2004 10:59 AM
Re: Motif debugger and KDE on cygwin
I think this must be the key. Unfortunately, I think it's probably due to some kind of cygwin oddity, but I still don't want to give up.
> Check in which state is the debugger
> process.
LEF
> Also try to change to another virtual
> desktop and then return to yours current
> virtual desktop.
Doesn't help but I finally got it to appear by launching the "desktop pager". From that application I was able to click on the debugger window and it appeared!
Thanks to all who contributed to this thread!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2004 01:43 AM
тАО10-12-2004 01:43 AM
Re: Motif debugger and KDE on cygwin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2004 08:42 AM
тАО10-12-2004 08:42 AM
Re: Motif debugger and KDE on cygwin
It seam that this (or similar) error was documented in some other circumstances. You can see some descriptions using Google with IsUnMapped.
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2004 10:06 AM
тАО11-15-2004 10:06 AM
Re: Motif debugger and KDE on cygwin
Thanks to all for your help!
I am reopening this thread in order to provide the following in case it might be useful to someone.
P.S. I finally solved this in a slightly more satisfactory manner.
I got a hold of the January 2005 edition of HP OpenVMS Debugger Manual. It has this:
!
! STARTUP RESOURCES: 3=Iconified, 0=Visible
!
DebugSource.initialState: 0
DebugControl.initialState: 0
DebugEditor.initialState: 0
DebugInstruction.initialState: 0
After adding the above to my DECW$USER_DEFAULTS:VMSDEBUG.DAT file but changing the 0s to 1s I can now run the XWindows debugger and it the debug window appears immediately.
So, I guess either this is a documentation bug or perhaps the Alpha OpenVMS 7.3-108 debugger is out of step w.r.t. the configuration file.