Path: news.cs.au.dk!not-for-mail From: Kasper Ligaard Nielsen Newsgroups: daimi.beta Subject: Re: BetaDBC og PostgreSQL Date: Fri, 19 Feb 1999 19:00:59 +0100 Organization: University of Aarhus, Department of Computer Science (DAIMI) Lines: 151 Message-ID: <36CDA6DB.127A9FEE@cs.au.dk> References: <36C943BD.D6A0F9EF@cs.au.dk> <36C9AA05.25D1DE7D@cs.au.dk> NNTP-Posting-Host: numerianus.cs.au.dk Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------63AECE111009E5261DE249EC" X-Trace: xinwen.cs.au.dk 919447259 1140 255.255.255.255 (19 Feb 1999 18:00:59 GMT) X-Complaints-To: news@cs.au.dk NNTP-Posting-Date: 19 Feb 1999 18:00:59 GMT X-Mailer: Mozilla 4.5C-SGI [en] (X11; U; IRIX 6.5 IP32) X-Accept-Language: en Xref: news.cs.au.dk daimi.beta:10392 This is a multi-part message in MIME format. --------------63AECE111009E5261DE249EC Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Klaus Marius Hansen wrote: > - har du gjort som der står i dProg2-FAQ'en? Ja, dog er jeg lidt i tvivl om hvor meget det dækker over når der står at man skal:"...installere og kompilere en driver-manager (iODBC). Denne kan hentes som..."? Jeg har hentet den fil du angiver, udpakket den, kørt sh og kørt ./build linux-elf og fik som resultat en iodbc.so.0.25 fil -- ganske som tutorialen foreskriver, men skal der ikke gøres mere? Skal filen ikke ligge et bestemt sted eller henvises til fra en eller anden konfiguretionsfil? (den medfølgende readme fil er ikke meget bevendt) > - har du prøvet med de simple eksempler i tutorial/ så som > tutorial/simple.bet? Jeps og jeg fik denne melding: [/users/kursus/dprog2/BetaDBC/tutorial]$ simple motorregister root foo **** Exception processing openConnectionException Missing server name, port, or database name in call to CC_connect. IM0021 # Beta execution aborted: Stop is called. # Look at 'simple.dump' [/users/kursus/dprog2/BetaDBC/tutorial]$ Jeg har attachet simple.dump. Jeg har prøvet med adskillige udgaver af .odbc.ini, bla. disse to: 1) [MotorRegister] Driver = /users/kursus/dprog2/RDB/lib/libcliPG.so Database = root Servername = localhost ReadOnly = 0 2) Denne har jeg strikket sammen ud fra den dokumentation, der følger med PostgreSQL: [ODBC Data Sources] MotorRegister = Read/Write Database [MotorRegister] Driver = /usr/local/pgsql/lib/libpsqlodbc.so Database = root Servername = localhost Port = 5432 ReadOnly = 0 [ODBC] InstallDir = /users/kursus/dprog2/RDB/lib hvor jeg i begge to har prøvet driver filerne alle kombinationer af de tre filer libcliPG.so, libpsqlodbc.ini og iodbc.ini . NB: Angående postmaster. Jeg bruger det script, der følger med PostgreSQL, til at starte/respawn'e postmaster. Jeg har ladet scriptet stå så det benytter unix sockets (de er kompileret med i kernel); desuden har jeg også prøvet med internet sockets men også uden held. mvh Kasper L. Nielsen --------------63AECE111009E5261DE249EC Content-Type: text/plain; charset=us-ascii; name="simple.dmp" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="simple.dmp" Beta execution aborted: Stop is called. Call chain: (linux) { PC 0x808d497, object 0x400e1eec, proto 0x80b1e74 } item in ~beta/basiclib/private/betaenvbody { Surrounding object 0x400e1ed4, proto 0x80b1e74 } -- stop# in ~beta/basiclib/betaenv { PC 0x8067696, object 0x400e1ed4, proto 0x80a230a } item in ~beta/basiclib/betaenv { Surrounding object 0x400e0020, proto 0x80a230a } -- BETAENV-~ in ~beta/basiclib/betaenv { PC 0x80675cd, object 0x400e1394, proto 0x80b3390 } item openConnectionException#BetaDBCException# in ~beta/basiclib/betaenv { Surrounding object 0x400e0020, proto 0x80b3390 } -- BETAENV-~ in ~beta/basiclib/betaenv { PC 0x807ed52, object 0x400e136c, proto 0x80a9bd2 } item in /users/kursus/dprog2/BetaDBC/private/betadbcbody { Surrounding object 0x400e11bc, proto 0x80a9bd2 } -- * in /users/kursus/dprog2/BetaDBC/private/betadbcbody { PC 0x807e92d, object 0x400e11bc, proto 0x80a9b28 } item <*> in /users/kursus/dprog2/BetaDBC/private/betadbcbody { Surrounding object 0x400e1014, proto 0x80a9b28 } -- open# in /users/kursus/dprog2/BetaDBC/betadbc { PC 0x807e811, object 0x400e1014, proto 0x80b3354 } item in /users/kursus/dprog2/BetaDBC/private/betadbcbody { Surrounding object 0x400e0b00, proto 0x80b3354 } -- Connection# in /users/kursus/dprog2/BetaDBC/betadbc { PC 0x808e241, object 0x400e0af0, proto 0x80b2060 } comp in /users/kursus/dprog2/BetaDBC/tutorial/simple { Surrounding object 0x400e0020, proto 0x80b2060 } -- BETAENV-~ in ~beta/basiclib/betaenv basic component in ~beta/basiclib/betaenv Legend: The above dump shows the dynamic call stack of invoked objects. The dump starts at the object that was the current object when the error occurred and continues down towards the basic component. The descriptions have the following meaning: 1. Items are shown in two lines, like this: item pname1#pname2#pname3 in ifile -- sname#spname1#spname2 in sfile meaning that the item is an instance of the descriptor "name" which has prefix "pname1" which has prefix "pname2", etc. This item is defined in the file "ifile". The part of the prefix chain enclosed in "<" and ">" indicates where in the action sequence the error occurred. The line beginning with "--" shows the textually surrounding descriptor using the same notation. 2. The descriptor names used in the above description will normally have one or more "meta characters" appended. The meaning of these is: # The descriptor belongs to a pattern, e.g. P: (# ... #) ~ Singular named descriptor, e.g. X: @(# ... #) * Singular unnamed descriptor, e.g. ... ; (# ... #) ; ... - Descriptor SLOT. 3. Components are shown using a notation similar to that of items, like this: comp pname1#pname2#pname3 in cfile 4. The bottommost component corresponding to the basic environment is shown like an ordinary component, but indicated with "basic component". 5. In case the error occurred in some external code called from BETA, the top of the call stack is shown as [ EXTERNAL ACTIVATION PART ] 6. In case the BETA code has called some external code which has in turn called back into the BETA code, and the callback is still active at the point of the error, the intermediate call stack part is also shown as [ EXTERNAL ACTIVATION PART ] 7. The lines containing '{' and '}' are lowlevel information, which can normally be ignored. By setting setenv BETART SimpleDump these lowlevel lines in the dump can be suppressed. --------------63AECE111009E5261DE249EC--