[odb-users] Problem connecting a mysql server
niermann at informatik.uni-tuebingen.de
niermann at informatik.uni-tuebingen.de
Tue May 15 11:27:30 EDT 2012
Dear Boris,
I get a segmentation fault when I try to run the odb-tests (checked for
versions 1.8.0 and 2.0.0 with appropriate libs) on a mysql-server:
./driver --options-file ../../db.options
BEGIN
INSERT INTO `auto_object` (`id`,`str`) VALUES (?,?)
INSERT INTO `auto_object` (`id`,`str`) VALUES (?,?)
INSERT INTO `auto_object` (`id`,`str`) VALUES (?,?)
COMMIT
BEGIN
SELECT `auto_object`.`id`,`auto_object`.`str` FROM `auto_object` WHERE
`auto_object`.`id`=?
ROLLBACK
./../../tester: line 35: 28986 Segmentation fault (core dumped)
./driver --options-file "$top_builddir/db.options" > test.out
FAIL: ../../tester
============================================
1 of 1 test failed
Please report to odb-users at codesynthesis.com
============================================
I looked up the mysql-logs:
120515 16:44:49 479 Connect
niermann at bsnode02.Informatik.Uni-Tuebingen.De on PIBI5
479 Query select @@version_comment limit 1
479 Query DROP TABLE IF EXISTS `auto_auto_only`
479 Query DROP TABLE IF EXISTS `auto_object`
479 Query CREATE TABLE `auto_object` (
`id` BIGINT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT,
`str` TEXT NOT NULL)
ENGINE=InnoDB
479 Query CREATE TABLE `auto_auto_only` (
`id` BIGINT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT)
ENGINE=InnoDB
479 Quit
120515 16:44:50 480 Connect
niermann at bsnode02.Informatik.Uni-Tuebingen.De on PIBI5
480 Query begin
480 Prepare INSERT INTO `auto_object` (`id`,`str`)
VALUES (?,?)
480 Reset stmt
480 Execute INSERT INTO `auto_object` (`id`,`str`)
VALUES (0,0)
480 Reset stmt
480 Execute INSERT INTO `auto_object` (`id`,`str`)
VALUES (0,0)
480 Reset stmt
480 Execute INSERT INTO `auto_object` (`id`,`str`)
VALUES (0,0)
480 Query commit
480 Query begin
480 Prepare SELECT
`auto_object`.`id`,`auto_object`.`str` FROM
`auto_object` WHERE `auto_object`.`id`=?
480 Reset stmt
480 Execute SELECT
`auto_object`.`id`,`auto_object`.`str` FROM
`auto_object` WHERE `auto_object`.`id`=0
After the SELECT statement the segfault occurs. I think even the INSERT
statements are not working right, since the inserted strings are all
empty.
I tried it for a 64bit linux machine with a 2.6.18-238.5.1.el5 kernel and
compiled the odb-tests with gcc (GCC) 4.6.1.
May this be related to the old kernel?
Since I'm not sure what causes the segmentation fault, do you have any
hints for me what I could try to get further information?
With kind regards,
Peter Niermann
More information about the odb-users
mailing list