I am sorry, you'll have to reopen the bug.
Version 5.0.36 still does NOT work.

There must be a pb on the debian port, or at least a pb on the compilation process for the ARM architecture.

Or an unproperly linked library... Or anything else.
But it requires investigation.

Nothing changed from the last time I had the pb (except mysql version). The gdb backtrace is exactly the same.
The home compiled mysql version is fine (from mysql sources).
The debian compiled package crashes.


regards

Martin Riondet
====================================================
# gdb /usr/sbin/mysqld
GNU gdb 6.6-debian
[...] GDB start
This GDB was configured as "arm-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run --defaults-file=/etc/mysql/my.cnf
[...] server start
[New Thread 147466 (LWP 13693)]
070329  1:23:39 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.36-Debian_1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution
[New Thread 163851 (LWP 13695)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 163851 (LWP 13695)]
0x001de32c in JOIN::exec ()
(gdb) backtrace
#0  0x001de32c in JOIN::exec ()

#1  0x001dfa10 in mysql_select ()
#2  0x001e0234 in handle_select ()
#3  0x00196480 in mysql_execute_command ()
#4  0x00199b2c in mysql_parse ()
#5  0x0019a13c in dispatch_command ()
#6  0x0019b21c in do_command ()
#7  0x0019bc50 in handle_one_connection ()
#8  0x40074fb0 in pthread_start_thread () from /lib/libpthread.so.0
Backtrace stopped: frame did not save the PC
(gdb)
#0  0x001de32c in JOIN::exec ()
#1  0x001dfa10 in mysql_select ()
#2  0x001e0234 in handle_select ()
#3  0x00196480 in mysql_execute_command ()
#4  0x00199b2c in mysql_parse ()
#5  0x0019a13c in dispatch_command ()
#6  0x0019b21c in do_command ()
#7  0x0019bc50 in handle_one_connection ()
#8  0x40074fb0 in pthread_start_thread () from /lib/libpthread.so.0
Backtrace stopped: frame did not save the PC
(gdb)


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to