Perrin Harkins wrote:
> On Sun, Dec 7, 2008 at 12:51 PM, Terence Monteiro
> wrote:
>> I'm getting segmentation faults with apache child processes. I'm running a
>> Catalyst application using DBIx::SearchBuilder in the backend to accesss a
>> mysql database.
>
> My guess is that you're opening dat
André Warnier wrote:
> Terence Monteiro wrote:
> [...]
> Hi.
> I cannot help you, but if you want help quickly, it helps if you provide
> some additional information, like :
> - which platform (Windows, Unix, Linux, version ?)
> - which version of Apache, and from where it comes
> - which version o
On Sun, Dec 7, 2008 at 12:51 PM, Terence Monteiro
<[EMAIL PROTECTED]> wrote:
> I'm getting segmentation faults with apache child processes. I'm running a
> Catalyst application using DBIx::SearchBuilder in the backend to accesss a
> mysql database.
My guess is that you're opening database handles
Terence Monteiro wrote:
[...]
Hi.
I cannot help you, but if you want help quickly, it helps if you provide
some additional information, like :
- which platform (Windows, Unix, Linux, version ?)
- which version of Apache, and from where it comes
- which version of mod_perl, and from where it come
Terence Monteiro wrote:
> Terence Monteiro wrote:
>> Hi,
>>
>> I'm getting segmentation faults with apache child processes. I'm running a
>> Catalyst application using DBIx::SearchBuilder in the backend to accesss a
>> mysql database. I'm running this on a debian quad core CPU server with 4
>> gigs
Terence Monteiro wrote:
> Hi,
>
> I'm getting segmentation faults with apache child processes. I'm running a
> Catalyst application using DBIx::SearchBuilder in the backend to accesss a
> mysql database. I'm running this on a debian quad core CPU server with 4
> gigs RAM. I enabled core dumping an
Hi,
I'm getting segmentation faults with apache child processes. I'm running a
Catalyst application using DBIx::SearchBuilder in the backend to accesss a
mysql database. I'm running this on a debian quad core CPU server with 4
gigs RAM. I enabled core dumping and got a gdb backtrace as follows:
#
