RE: Core file (debugging info turned on/stack trace)

2000-09-28 Thread Doug MacEachern
On Tue, 26 Sep 2000, Shane Adams wrote: Well I did a little more investigation - it seems that we are dieing in Expat.pm line 451. The offending Function is: ... is this something you can reproduce at will? if you can give me a tiny test case that i can drop and i run, i'll take a look.

Core file (debugging info turned on/stack trace)

2000-09-26 Thread Shane Adams
Title: Core file (debugging info turned on/stack trace) Apache 1.3.12, mod_perl 1.24, Perl 5.6.0, Redhat 6.1 ... Program terminated with signal 11, Segmentation fault. ... 0 0x814abd4 in Perl_sv_setsv (dstr=0x8d34514, sstr=0x84afba4) at sv.c:2774 #1 0x813b6b3 in Perl_pp_sassign

RE: Core file (debugging info turned on/stack trace)

2000-09-26 Thread Shane Adams
Title: RE: Core file (debugging info turned on/stack trace) Well I did a little more investigation - it seems that we are dieing in Expat.pm line 451. The offending Function is: sub parse { my $self = shift; my $arg = shift; croak Parse already in progress (Expat) if $self-{_State_