Title: RE: Search Engine Theory
Check out the book "Managing Gigabytes"
Text indexing theory and algorithms. Source code too.
-Original Message-
From: Jamie Krasnoo [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 27, 2001 3:03 PM
To: Modperl
Subject: Search Engine Theory
C
Title: RE: Debugging mod_perl with gdb
Hey thanks. I'll try this. I tried the 'man gdb' command and it didn't help much I'm afraid...
-Original Message-
From: sterling [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 12:33 PM
To: Shane A
Title: Debugging mod_perl with gdb
Hey there -
I've successfully built apache/mod_perl with full debugging. In addition, I'm running the whole setup through insure, a commercial memory leak/corruption tool.
I've found a "write to a dangling pointer" when apache/mod_perl evaluates a sec
]Sent: Monday, October 09, 2000
3:59 PMTo: Shane Adams; '[EMAIL PROTECTED]'Subject: RE:
:Parse segmentation fault
This allows
for XML parsing with no change to the Perl code. I'm just not sure what
I am losing in Apache (which is where I make the change). What does
: Shane Adams; '[EMAIL PROTECTED]'Subject: RE:
:Parse segmentation fault
I did a
little more digging around and found that you could also avoid the problem by
turning off EXPAT in apache with:
Rule
EXPAT=no
Which fix
is more preferable?
-Original Messag
Title: RE: :Parse segmentation fault
Yes. We found a problem in Expat.pm line 451 (in sub parse). The following chunk of code (latest version from cpan)
sub parse {
my $self = shift;
my $arg = shift;
croak "Parse already in progress (Expat)" if $self->{_State_};
$self->{_State_} =
ng with typeglobs under an eval ... I believe that * is a typeglob in perl yes?
-Original Message-
From: Shane Adams
Sent: Tuesday, September 26, 2000 4:16 PM
To: [EMAIL PROTECTED]
Subject: Core file (debugging info turned on/stack trace)
Apache 1.3.12, mod_perl 1.24, Perl 5.6.0, Redhat
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 () at pp_ho
313 in main ()#23 0x400d31eb in
__libc_start_main (main=0x80a9fcc , argc=2,
argv=0xb944, init=0x8062820 <_init>, fini=0x81a73cc
<_fini>, rtld_fini=0x4000a610 <_dl_fini>,
stack_end=0xbffff93c) at
../sysdeps/generic/libc-start.c:90(gdb) q
-Original Message
lly try to fix this? The learning curve on trying
to understand the internals of perl is enormous!
-Original Message-From: Shane Adams Sent:
Friday, September 08, 2000 10:38 PMTo: ModperlSubject:
Core dumping
Hello -
I am experiencing a situation where apache core
dump
Title: Core dumping
Hello -
I am experiencing a situation where apache core dumps. We are using HTML-Mason. The relevant revision numbers are:
Apache_1.3.12
mod_perl-1.24
perl-5.6.0
HTML-Mason .87
redhat 6.1 (no patches)
Our apache server is built in 2 flavors, one that uses Mason, an
Title: RE: open(FH,'|qmail-inject') fails
Another approach to is to write the email directly into the queue. I've used this approach and it's very fast. After you write your email to the qmail queue, you write a value of 1 to a named pipe that qmail reads off of. This causes a qmail process
12 matches
Mail list logo
