I have 1.7.23 running simple1 just fine.

I just installed 1.7.32 and tried to run simple1 and it seg faults.

I have narrowed it down to the line:
mysqlpp::Result res = query.store();
in util.cpp.

I have read the thread from Marco/Chris/Warrent about his SegFaults.

Note: RHEL3 gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-49)
[root@dragon examples]# ldd .libs/lt-simple1
libmysqlpp.so.4 => /usr/local/src/mysql+
+-1.7.32/lib/.libs/libmysqlpp.so.4 (0x00ec5000)
libz.so.1 => /usr/lib/libz.so.1 (0x00a76000)
libmysqlclient.so.10 => /usr/lib/mysql/libmysqlclient.so.10
(0x00da1000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x00111000)
libm.so.6 => /lib/tls/libm.so.6 (0x00aaf000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00b39000)
libc.so.6 => /lib/tls/libc.so.6 (0x001c4000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x006b8000)
libnsl.so.1 => /lib/libnsl.so.1 (0x002fc000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00d3c000)
[root@dragon examples]# pwd
/usr/local/src/mysql++-1.7.32/examples

[root@dragon examples]# ./resetdb localhost root foo
Reinitialized sample database successfully.

[root@dragon examples]# ./simple1 localhost root foo
1
2
Query: select * from stock
a
Segmentation fault (core dumped)
[root@dragon examples]# ls -al core
ls: core: No such file or directory

Hmm... no core, but says it cores... hmm...

(You'll note I added old-school debugging "cout's" before each step to
get to that line is what is causing problems.)

--
Mike Kinney
www.RedAceSolutions.com
Phone (503) 590-5606 x201


--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw

I'm not sure what to recommend other than to re-check your build process
very carefully.

There's so many segfault reports on this list that mysql++ must be
really hard to use or something. :-) Mostly they are user error
or a really old compiler, or non-compliant compiler. But I'd sure like
to know if there is some underlying assumption in the code or makefiles
that help confuse the system.

A lot of problem reports seem to come from people with multiple versions
installed. You might want to move 1.7.23 out of harm's way (or tar it up
and delete it) and rebuild 1.7.32 completely.

As for core files, some systems name the core files with a PID number
attached.

If you find the cause, please do report back.

- Chris


On Fri, Mar 18, 2005 at 06:35:38PM -0800, Mike Kinney wrote:
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw

Mike Kinney wrote:
Since you're using Red Hat, I presume that this means you installed one
of the RPMs. If it was the binary, then...

....this is your problem. You're using MySQL 3.23 with a version of
MySQL++ linked against MySQL v4.0.

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw