| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
I have an X-11 server running on a Macintosh II and a DECwindows
application running on a VAX/VMS client. Everything works just
fine, but....when I attempt to select an application from the
application menu of a FILEVIEW, the FILEVIEW exits with an access
violation and a stack dump.
Here is my configuration:
MACintosh II, Community-MAC DECnet by EMAC, Exodus X.11
Server by White Pines software.
VAXserver 3800 running VMS V5.3 and DECwindows V2.0.
I can pull up the application seperately and it works fine
with a VMS run command eg
$ Create Display/Node=****
$ Run Sys$system:DecW$mail
It only fails when it is initiated through FILEVIEW.
Why do I get a access violation and stack dump? And how do I
work around this?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2182.1 | STAR::MFOLEY | Rebel Without a Clue | Thu Feb 01 1990 17:06 | 5 | |
You might try BULOVA::FILEVIEW also.. mike | |||||
| 2182.2 | Some speculation... | LNKUGL::BOWMAN | Bob Bowman, CSC/CS SPACE Team | Thu Feb 01 1990 19:13 | 10 |
Is it always an ACCVIO, or do you get a LIBINVMEM error? Does this crash happen immediately or only after you have been using DECW$MAIL? The reason I ask, is that I have qar'd a problem which appears to be connected to using Shift-MB1 in DECW$Mail (deselecting a global selection), followed by using a FileView menu option. FileView attempts to retrieve the global selection and gets information which says the size of this is -1, attempts to get virtual memory of this size, and the allocation fails. Eng. is researching this issue. | |||||
| 2182.3 | GOSOX::RYAN | DECwindows Mail | Fri Feb 02 1990 08:18 | 13 | |
>Eng. is researching this issue. Engineering has fixed this issue:-) (just in time for VMS V5.4 EFT). But that doesn't sound like .0's problem, which happens when the application is initiated... re .0: Whatever the cause, what you're seeing is a bug and should be QAR'd in the DECWINDOWS-IFT or V5 database on TRIFID. When you do so, try to include some of the useful information you omitted from your note (like the exact error message and stack dump). Mike | |||||