It appears that downgrading DBD::mysql to version 4.004 has done the trick.
Amiri
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17668030.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
What version were you using that was causing the problems?
amiribarksdale wrote:
It appears that downgrading DBD::mysql to version 4.004 has done the trick.
Amiri
--
Red Hot Penguin Consulting LLC
mod_perl/PostgreSQL consulting and implementation
http://www.redhotpenguin.com/
Fred Moyer wrote:
What version were you using that was causing the problems?
4.007.
Amiri
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17675687.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
I reinstalled mysql from source and recompiled my DBD::mysql against
its new libs, and I still get the same backtrace:
Using host libthread_db library /lib64/tls/libthread_db.so.1.
...
#0 0x002a994cf93e in mysql_send_query ()
from /home/mysql/lib/mysql/libmysqlclient.so.15
(gdb) bt
Does anyone have any guidance on what I should do here?
Amiri
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17627528.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
amiribarksdale wrote:
Does anyone have any guidance on what I should do here?
Amiri
From the archive thread: -
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17627528.html
Here are two short snippets of gdb output from the other evening. Can
someone lead me in the right direction
this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17628964.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
amiribarksdale wrote:
Yes, I moved from 32 bit to 64 bit. But I did exactly what you said. I
reinstalled everything--perl, apache, mysql, DBI, DBD::mysql, every single
module--the whole shebang. So it's not just some careless oversight or file
copy. Everything has already been rebuilt and
connection closing.
Apache::DBI disconnect (overloaded)
Try setting the debug level for Apache::DBI to 2 to get verbose output.
$Apache::DBI::DEBUG
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17631195.html
Sent from the mod_perl - General
amiribarksdale wrote:
No, they're not the same, because they cannot be the same any longer. In the
server migration, I had to recompile and reinstall everything, because of
those 32-bit and 64 bit errors. I just built everything back up from
barebones CentOS.
From my cursory look through the
amiribarksdale wrote:
Yes, I have the debug output on 2 already. It doesn't say much else than what
I posted.
Ah right, read DEBUG level in the thread, didn't get that you had
actually set the apache dbi debug level (despite the log entry clearly
indicating it).
Can you post your
',
),
);
sub handler {
my $r = shift;
$ah{$r-dir_config('site')}-handle_request($r);
}
1;
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17633171.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
, {SIG_DFL}, {SIG_DFL}, 8) = 0
kill(2396, SIGSEGV) = 0
rt_sigreturn(0x95c) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 2396 detached
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17599739.html
Sent from
,blurb,country,language,timezone,openid,pic...
table = Variable table is not available.
All my core dumps have this error about not being able to find the table!
That's a big clue, but where it leads, I don't know.
Amiri
--
View this message in context:
http://www.nabble.com/Segfault
-multi/auto/XML/LibXML/LibXML.so
#0 0x002a994e37be in mysql_send_query ()
from /usr/lib64/mysql/libmysqlclient.so.15
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17613827.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
15 matches
Mail list logo
