🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.vms
Article #15823

Re: problems with PEX

#15823
From: Karl Schultz
Date: Thu, 23 Jan 1997 00:00
116 lines
5018 bytes
Andreas Hetfeld wrote:
> 
> --
> ------------------------------------------------------------------------------
>   $HOME                             $WORK
> Andreas Hetfeld                   Lehrstuhl fuer Elektrische Energieversorgung
> Am Koehler 12 A                   Bergische Universitaet Wuppertal
> 42349 Wuppertal                   Fuhlrottstrasse 10
> Hi everybody,
> 
> I've got some problems building a programm (listing see below) using pexlib:
> after compiling and linking I started the programm and got the following
> error message:
> 
> $ run plcube
> X Error of failed request:  154
>   Major opcode of failed request:  139 (X3D-PEX)
>   Minor opcode of failed request:  43 ()

If you look in PEX.h, you can see that 43 is the request code for
StoreElements, which suggests that something is wrong with
your structure.

Read on.

> Serial number of failed request:  6
>   Current serial number in output stream:  7
> %XLIB-E-ERROREVENT, error event received from server
> %TRACE-E-TRACEBACK, symbolic stack dump follows
>  Image Name   Module Name     Routine Name    Line Number  rel PC      abs PC
>                                                         0 80758320    80758320
>                                                         0 80758510    80758510
>                                                         0 8075B7CC    8075B7CC
>                                                         0 8075A108    8075A108
>                                                         0 806E3114    806E3114
>  PLCUBE       PLCUBE          main                  11650 000008E4    000308E4
>  PLCUBE       PLCUBE          __main                    0 00000058    00030058
>                                                         0 84DE0170    84DE0170
> 
> In the debugger session I got the following error executing the funktion
> 
> XSync(theDisplay,0);

This just means that the requests were batched up on the client side and
not sent to the server until XSync.  The problem could therefore be
with any of the batched requests.  There are ways (see XSynchronize)
that will force each request to the server one at a time, which may
make debugging easier.

> 
> %DEBUG-W-SCRNOSRCLIN, no source line for address 80758320 for display in Source View
> %XLIB-E-ERROREVENT, error event received from server
> break on unhandled exception preceding SHARE$DECW$XLIBSHR_CODE0+549664
> 
> I compiled and linked the programm with the following options:
> 
> $ cc /float=ieee_float plcube.c /include=sys$common:[decw$include.pex5] -
>      /stand=vaxc
> 
> $ link plogo,pex.opt/opt
> 
> pex.opt:
> 
> sys$share:decw$mitpexlibshr/share
> sys$share:decw$xlibshr/share
> 
> Working environment: DEC alpha station 250 4/266, OpenVMS V6.2, OPEN3DPEX
> server extension installed
> 
> I tested the pex server extension by running the example @sys$test:pst_cube.com
> without any error.
> 
> What's wrong, how can I fix this problem?
> 
> By the way: what's to do to let the precompiler command
> #include <X11/PEX5/PEXlib.h> work on my OpenVMS system?

The standard way is to use a -I C compiler directive
to point to the directory that has X11/PEX5/PEXlib.h in it.


For example, suppose somebody installed X on your system
in a directory called /usr/X11R6 and one of the directories
in /usr/X11R6 is X11/PEX5.  Then, you would say -I/usr/X11R6.


<program snipped>

I didn't see a PEXCreateStructure call in your program.

Structures are PEX/X resources, so you must explicitly
create them.  When you create a structure, you 
get back a resource ID that is subsequently used
to access the structure.

Since you are getting an error when you try to
store data in a structure, it is probably because
you have not created it.

The code you have to accept a structure number
via the command line won't work.

You need something like:

PEXStructure mystrux;

...

PEXInitialize(...)

...

mystrux = PEXCreateStructure(display);

now start loading the structure.
Technical Details
Message-ID: <32E79267.5248@fc.hp.com>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <5c7bvf$83s@wmwap1.math.uni-wuppertal.de>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f7344,8b59b1300d800f5f
X-Google-Attributes: gidf7344,public
X-Google-Thread: 10f8a1,8b59b1300d800f5f
X-Google-Attributes: gid10f8a1,public
X-Google-Thread: 1028ef,8b59b1300d800f5f
X-Google-Attributes: gid1028ef,public
X-Google-Thread: fce35,8b59b1300d800f5f
X-Google-Attributes: gidfce35,public
X-Google-Thread: 115ff0,8b59b1300d800f5f
X-Google-Attributes: gid115ff0,public
From: Karl Schultz <kws@fc.hp.com>
Subject: Re: problems with PEX
Date: 1997/01/23
Message-ID: <32E79267.5248@fc.hp.com>
X-Deja-AN: 211717634
references: <5c7bvf$83s@wmwap1.math.uni-wuppertal.de>
to: Andreas Hetfeld <HETFELD@WEEEV3.UNI-WUPPERTAL.DE>
content-type: text/plain; charset=us-ascii
organization: Hewlett-Packard
mime-version: 1.0
newsgroups: comp.os.vms,vmsnet.alpha,comp.graphics.api.pexlib,fj.sys.vax,fj.sys.alpha
x-mailer: Mozilla 3.0Gold (X11; I; HP-UX B.10.20 9000/725)