[HELP]What is the rule for the order of those tags in curl-loader

[邹靖晗 <zou...@gm...>]

Hi all,

     I am using curl-loader to try some network test, I use perl to drive
the test. I saved the general tags and a set of url tags in a hash table,
then use foreach to loop the hash table to output the configuration file
for curl-loader. So the order of tags is based on the hash method in perl.
Then I run curl-loader -f <the configuration file> and get a core dump.

    Seems the order for the tags will impact the test result. So I want to
know what is the rule for the order of these tags in curl-loader?



Here is the configuration file:

[root@localhost jhzou]# cat 10.conf
CYCLES_NUM=-1
INTERFACE=eth1
CLIENTS_NUM_START=10
URLS_NUM=1
IP_ADDR_MIN=10.1.1.130
CLIENTS_RAMPUP_INC=5
BATCH_NAME=default_test
NETMASK=255.255.255.0
IP_ADDR_MAX=10.1.1.149
CLIENTS_NUM_MAX=20



TIMER_URL_COMPLETION=0
URL=http://10.1.1.122/index.htm
URL_SHORT_NAME=default_url
TIMER_AFTER_URL_SLEEP=0
REQUEST_TYPE=GET


This is the core dump debug informantion

Program received signal SIGSEGV, Segmentation fault.
timer_url_completion_parser (bctx=0x7ffffffe0b00, value=<value optimized
out>) at parse_conf.c:1899
1899
bctx->url_ctx_array[bctx->url_index].timer_url_completion_hrange =
(gdb) p bctx->url_index
$1 = 0
(gdb) p  bctx->url_ctx_array[bctx->url_index]
Cannot access memory at address 0x0
(gdb) bt
#0  timer_url_completion_parser (bctx=0x7ffffffe0b00, value=<value
optimized out>) at parse_conf.c:1899
#1  0x000000000041c45f in add_param_to_batch (filename=<value optimized
out>, bctx_array=0x7ffffffe0b00,
    bctx_array_size=64) at parse_conf.c:416
#2  parse_config_file (filename=<value optimized out>,
bctx_array=0x7ffffffe0b00, bctx_array_size=64)
    at parse_conf.c:2897
#3  0x000000000040c524 in main (argc=<value optimized out>,
argv=0x7fffffffe588) at loader.c:159

-- 
Sincerely yours,
Zou Jinghan