Thanks all for the replys.

I see that I am using an older DBD-Ingres, rev 0.21, in my existing Perl
5.005.03 installation.  

I'm in process of upgrading my perl to perl 5.6.0 with the crinoid
patchset collection, so I'm recompiling all my modules too.

If I can't get DBD-Ingres 0.26 working today, I may try falling back to
my known working version 0.21 - at least if I can find the tarball for
it. :-)  Also, I'll try the 0.26 revision against our Ingres II
installation (the bug report I gave is for Ingres 6.4/05), and with a
different decc version (5.2-003 or 5.5-002 instead of 6.0-001)

Meanwhile, here's what I've found out last night:

According to the VMS debugger, the routine is dying in the dXSARGS
statement in the expanded XS boot routine, which I snip and include
below.  I'm not certain how to show the exact statement it bombs on
here. :-(

  XS(boot_DBD__Ingres)
  {
      dXSARGS;
      char* file = __FILE__;

The debugger says it's being called from this line in the module PP_HOT,
routine Perl_pp_entersub:

            /* Do we need to open block here? XXXX */
            (void)(*CvXSUB(cv))(aTHXo_ cv);

Here's the last bit of a run of t/dbi.t with the /map qualifier added to
the dbd-ingres's descrip.mms link flags, with DBI_TRACE and
PERL_DL_TRACE set to high values.

Testing: DBI->connect('dbi:Ingres:development::cts_development'):
    -> DBI->connect(dbi:Ingres:development::cts_development, , ****,
HASH(0x1f9d
64))
    -> DBI->install_driver(Ingres) for perl=5.006 pid=1342282173
ruid=4718663 eu
id=4718663
DynaLoader::bootstrap for DBD::Ingres (:auto:DBD/Ingres:Ingres.exe)
dl_expand_filespec([.blib.arch.auto.DBD.Ingres]Ingres.exe):
        SYNCHK sys$parse = 65537
        split filespec: name = INGRES, default =
CTSNDB08:[PERL-MODULES.DBD-INGR
ES-0_26.BLIB.ARCH.AUTO.DBD.INGRES].EXE;
        name/default sys$parse = 65537
        sys$search = 65537
        result =
\CTSNDB08:[PERL-MODULES.DBD-INGRES-0_26.BLIB.ARCH.AUTO.DBD.INGR
ES]INGRES.EXE;6\
dl_load_file(CTSNDB08:[PERL-MODULES.DBD-INGRES-0_26.BLIB.ARCH.AUTO.DBD.INGRES]IN
GRES.EXE;6,0):
        VMS-ified filespec is
CTSNDB08:[PERL-MODULES.DBD-INGRES-0_26.BLIB.ARCH.A
UTO.DBD.INGRES]INGRES.EXE;6
        sys$filescan: returns 1, name is INGRES
        libref = name: INGRES, defspec:
CTSNDB08:[PERL-MODULES.DBD-INGRES-0_26.B
LIB.ARCH.AUTO.DBD.INGRES].EXE;6
        $dl_require_symbols[0] = boot_DBD__Ingres
        lib$find_image_symbol returns 1
dl_find_dymbol(INGRES,boot_DBD__Ingres):
        lib$find_image_symbol returns 1
        entry point is 3835504
dl_install_xsub(name=DBD::Ingres::bootstrap, symref=3a8670)
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=000000000000
0000, PC=00000000003DAEFC, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
  image    module    routine             line      rel PC           abs
PC
 INGRES  INGRES  boot_DBD__Ingres       50307 0000000000002EFC
00000000003DAEFC
 DBGPERLSHR  PP_HOT  Perl_pp_entersub   52151 000000000000B350
0000000000145BD0
 DBGPERLSHR  RUN  Perl_runops_debug     45128 0000000000000210
0000000000111480
 DBGPERLSHR  PERL  S_run_body           46559 00000000000032A8
00000000000A9E88
 DBGPERLSHR  PERL  perl_run             46483 0000000000002F0C
00000000000A9AEC
 PERL  PERLMAIN  main                   45124 00000000000001C0
00000000000201C0
 PERL  PERLMAIN  __main                     0 00000000000000A0
00000000000200A0

-- Pat

Henrik Tougaard wrote:
> 
> Just wondering: have you had success with *any* version of DBD::Ingres??
> I just checked and am <blush> deeply embarrassed </blush> to discover that
> we use version 0.16 on VMS.
> 
> There must have been problems with the later versions - MakeMaker did bother
> me a bit, as did DBI versions later than 1.00. VMS is a lopw-priority
> platform here I'll have to have a look at that real soon now...
> 
> I'll try to do a test as soon as the project I'm working on now gives me
> some time to fiddle with it.
> 
> Henrik Tougaard, FOA, Copenhagen, Denmark.  [EMAIL PROTECTED] - aka.
> [EMAIL PROTECTED]
> DBD::Ingres maintainer.

-- 
      This message does not represent the policies or positions
             of the Mayo Foundation or its subsidiaries.
  Patrick Spinler                       email:  [EMAIL PROTECTED]
  Mayo Foundation                       phone:  507/284-9485

Reply via email to