tpcc_start segfaults

Bug #840508 reported by Baron Schwartz
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
percona-tools
New
Undecided
Unassigned

Bug Description

tpcc_start segfaults for me on Fedora 15, 32-bit machine. Here are the arguments and output:

[baron@ginger tpcc-mysql]$ LD_LIBRARY_PATH=/home/baron/etc/mysql/server/5.1.50/lib/ ./tpcc_start localhost tpcc1000 root "" 5 5 30 30
***************************************
*** ###easy### TPC-C Load Generator ***
***************************************
<Parameters>
     [server]: localhost
     [port]: 3306
     [DBname]: tpcc1000
       [user]: root
       [pass]:
  [warehouse]: 5
 [connection]: 5
     [rampup]: 30 (sec.)
    [measure]: 30 (sec.)

RAMP-UP TIME.(30 sec.)
Segmentation fault (core dumped)

When I run it in GDB, I see the following.

[New Thread 0xb7fe6b70 (LWP 4857)]
[Thread 0xb7fe6b70 (LWP 4857) exited]
[New Thread 0xb7fe6b70 (LWP 4858)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7fe6b70 (LWP 4858)]
0x00167774 in my_stat (
    path=0xb7fe50f2 "/usr/local/mysql/share/charsets/Index.xml",
    stat_area=0xb7fe506c, my_flags=0) at my_lib.c:540
540 my_lib.c: No such file or directory.
 in my_lib.c

I don't have MySQL installed on this laptop. I just have it untarred and running in my home directory. It looks like the MySQL libraries expect things to be placed into a specific directory. When I link from there to my tarball, it works okay. Can this be avoided, or is tpcc_start or the MySQL library simply not checking for its required files correctly or something? If this is a bug in the MySQL libraries, I can report it upstream.

Revision history for this message
Richard Bensley (richardbensley) wrote :

I am also getting a segmentation fault on RHEL:

xxxxxx@xxxxxx> uname -r
2.6.32-220.7.1.el6.x86_64
xxxxxx@xxxxxx> cat /proc/cpuinfo | grep processor | wc -l
80
xxxxxx@xxxxxx> cat /proc/meminfo | grep MemTotal
MemTotal: 264516692 kB
xxxxxx@xxxxxx> ldd tpcc_start
        linux-vdso.so.1 => (0x00007fffcd4fd000)
        libmysqlclient.so.18 => /data/mysql/lib/libmysqlclient.so.18 (0x00007f300bdb1000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f300bb88000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f300b904000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f300b6fc000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f300b4f7000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f300b167000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f300c210000)
xxxxxx@xxxxxx> ./tpcc_start localhost:3101 tpcc1000 root password 100 10 16 3600
***************************************
*** ###easy### TPC-C Load Generator ***
***************************************
non-option ARGV-elements: localhost:3101 tpcc1000 root password 100 10 16 3600
<Parameters>
     [server]:
     [port]: 3306
     [DBname]: tpcc
       [user]:
       [pass]:
  [warehouse]: 1
 [connection]: 10
     [rampup]: 10 (sec.)
    [measure]: 20 (sec.)

RAMP-UP TIME.(10 sec.)
Segmentation fault

strace also shows that it doesn't pickup any parameters.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.