MySQL-python 1.2.0 and mod_python 2.7.11?
MySQL database connector for Python programming
Brought to you by:
adustman
Menu
▾
▴
Hi, for the past few days I've been trying to get MySQL-python 1.2.0 working with mod_python and I've been plagued with a segfault that I can't find. I was wondering if you'd heard of any problems like this. Here's my setup:
RedHat 9.0
Apache 1.3.27
mod_python 2.7.11
MySQL-python 1.2.0
Python 2.4.2
MySQL 4.1.18
I'm trying to upgrade from:
MySQL 4.0.20
MySQL-python 0.9.1
Everything is working in the old setup, but as soon as I updated MySQL and MySQL-python I started getting segfaults. I'm not loading mod_php so I'm pretty sure it's not the problem detailed here: http://www.modpython.org/FAQ/faqw.py?req=all#2.13 Now I do have a couple of other modules that link against MySQL, but I recompiled them and made sure they were linked against the same library as _mysql.so. I'm completely stumped.
Using gdb I was able to get the following traceback. I'm not sure if it'll really help, but it's all I've got. I'd appreciate any help you can give me, even if it's just to tell me that my current configuration is whacked and I need a kick in the ass. :)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1074994272 (LWP 25564)]
0x4207457b in _int_malloc () from /lib/tls/libc.so.6
(gdb) where
0 0x4207457b in _int_malloc () from /lib/tls/libc.so.6
1 0x4207378d in malloc () from /lib/tls/libc.so.6
2 0x420739b2 in realloc () from /lib/tls/libc.so.6
3 0x420c6716 in create_cd_newstate () from /lib/tls/libc.so.6
4 0x420c360f in build_trtable () from /lib/tls/libc.so.6
5 0x420c06cc in transit_state () from /lib/tls/libc.so.6
6 0x420be0ca in check_matching () from /lib/tls/libc.so.6
7 0x420bd93b in re_search_internal () from /lib/tls/libc.so.6
8 0x420bce67 in regexec () from /lib/tls/libc.so.6
9 0x0806ba6b in ap_regexec (preg=0x814f7f8, string=0x814f7f8 "",
nmatch=135591928, pmatch=0x814f7f8, eflags=135591928) at util.c:374
10 0x08068d60 in location_walk (r=0x81a27b0) at http_request.c:681
11 0x0806996b in process_request_internal (r=0x81a27b0) at http_request.c:1208
12 0x08069d2b in ap_process_request (r=0x81a27b0) at http_request.c:1338
13 0x08061928 in child_main (child_num_arg=135591928) at http_main.c:4690
14 0x08061b07 in make_child (s=0x814f7f8, slot=0, now=135591928)
at http_main.c:4869
15 0x08061e49 in perform_idle_server_maintenance () at http_main.c:5051
16 0x08062785 in standalone_main (argc=44, argv=0xbfffe474)
at http_main.c:5288
17 0x08062b80 in main () at http_main.c:5567
18 0x42015704 in __libc_start_main () from /lib/tls/libc.so.6
I'm sorry that I'm not sure but basically I can say 2 things.
First is that I'm using Mysql Apache and Python respectively with version 5.0 2.0 and 2.4.3 and it's possible to use mod_python and mysql-python linking modules (those 2 programs basically are joining tools between apps).
Second I think that your configuration is really broken in malloc program and probably it could be a memory error if (after installing a new o.s. for example a live linux) you will have strange error like this in basic libraries (standard C library for allocating memory)
What versions of Apache and mod_python are you using? My main concern is that my old (1.3) version of Apache and corresponding mod_python are causing the problem.