On 3 Apr 2002, Jason E. Stewart wrote:

> "Steven N. Hirsch" <[EMAIL PROTECTED]> writes:
> 
> > On 3 Apr 2002, Jason E. Stewart wrote:
> > 
> > > "Steven N. Hirsch" <[EMAIL PROTECTED]> writes:
> > > 
> > > > Something is quite broken with the XS SWIG_init() function under
> > > > AIX.  The shared .so just coredumps on load 100% of the time.  I've
> > > > made a few iterations through with different compiler options, but
> > > > no luck.
> > > > 
> > > > It's going down in Perl_pp_entersub() (pp_hot.c line 2618 - Perl 5.6.1):
> > > > 
> > > > (void)(*CvXSUB(cv))(aTHXo_ cv)  <---
> > > > 
> > > > Where (I'm guessing) it's trying to initialize the XS module.  I notice 
> > > > that this section of the code has changed quite a bit since 1.5.2.
> > > > 
> > > > Seems like it must be quite fundamental, but nothing jumps out at me.
> > > 
> > > Bummer.
> > > 
> > > Was this with xlC or with gcc?
> > 
> > With VAC 5.x xlC.
> 
> The only thing I can think of is that it's a perl issue. Do you have
> access to another version of Perl, like 5.7.2? If it reproduces there,
> it's a SWIG issue.

Actually, it's starting to look like a problem with how my Perl build 
deals (or fails to deal) with shared C++ objects built by VAC xlC.

I rebuilt using the old xlC "CSet++" 3.6.x compiler and it works as well 
as it ever did on AIX: The exception handling tests dump core right and 
left while everything else is just fine.

I even tried building a single-threaded version of Xerces-C, but that made 
no difference.

One of these days I'll find the time to beat this into submission.

Steve

-- 
----------------------------------------------------------------
Steven N. Hirsch       tie-line: 446-6557     ext: 802-769-6557

Staff Engineer                     Methodology Integration Team
ASIC Product Development           IBM Microelectronics
----------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to