Hm. There must be some problem with my machine. After
building and reinstalling a new version of perl (in
/usr/local/perl-5.6.1) and reinstalling all my needed
perl modules, I still get the same exact error as
before (detailed below).
System is RedHat 7.2, updated with secirity patches.
Looks like I'm going to have to reinstall the system
to resolve this.
--- J Robinson <firstname.lastname@example.org> wrote:
> --- email@example.com wrote:
> > On Fri, Nov 14, 2003 at 06:30:07AM -0800, J
> > wrote:
> > >
> > > I have been able to reproduce the segfault from
> > the
> > > command line using my SWISH::API client.
> > the
> > > resulting core dump file always leads to a call
> > > 'chunk_free()' -- here's a typical stack trace:
> > That's ugly.
> > So you cannot make it happen with the swish-e
> > binary, right? There's
> > not a huge difference in the way the binary and
> > C API work. And
> > there's not a lot of work going on in the API.xs
> > code. Did you try with
> > a different version of Perl?
> > Yep, ugly. I would try different version of Perl.
> > Since you suspect
> > large properties, maybe build --without-zlib and
> > reindex and try again.
> > It would be really great if you could get the
> > segfault outside of Perl.
> You're right, I couldn't reproduce the error with
> SWISH-E binary, nor on another machine using the
> code. I suspect you're right, something's gone
> in my perl install. I'll try rebuilding and
> reinstalling perl, thanks for feedback.
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
Received on Sat Nov 15 13:59:21 2003