Problem with curl-loader on ubuntu 64bit

[Robert I. <cor...@gm...>]

Hi Sergei,

On Fri, Oct 10, 2008 at 9:57 AM, Sergei Sh <ser...@qi...> wrote:

> Hi
> I have problem running curl-loader on ubuntu: Linux server 2.6.24-19-server
> #1 SMP Wed Aug 20 18:43:06 UTC 2008 x86_64 GNU/Linux
> But it successful runs on other machine: Linux private 2.6.24-19-generic #1
> SMP Wed Aug 20 22:56:21 UTC 2008 i686 GNU/Linux
>
> when I run on the server:
> ./curl-loader -f conf-examples/10K.conf -
>
> parse_config_file - error: failed to load even a single batch.
> main - error: parse_config_file () failed.
>
> This is problem with both 0.44 and 0.46. But on the my PC (i686) both
> versions run perfectly..
> May it be problem with x86_64?? It's only the difference I can see here.
>
> This is from stracing:
>
> stat("conf-examples/10K.conf", {st_mode=S_IFREG|0644, st_size=617, ...}) =
> 0
> brk(0)                                  = 0x677000
> brk(0x698000)                           = 0x698000
> open("conf-examples/10K.conf", O_RDONLY) = 3
> fstat(3, {st_mode=S_IFREG|0644, st_size=617, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7f0767c0b000
> read(3, "########### GENERAL SECTION ####"..., 4096) = 617
> read(3, "", 4096)                       = 0
> close(3)                                = 0
> munmap(0x7f0767c0b000, 4096)            = 0
> write(2, "parse_config_file - error: faile"..., 63) = 63
> write(2, "main - error: parse_config_file "..., 43) = 43
> exit_group(-1)                          = ?
>
> --
> Sergei Sh.
>


Thanks for your reporting.

Please, kindly, subscribe to the mailing list:
https://lists.sourceforge.net/lists/listinfo/curl-loader-devel
and make your further postings to the list.
We have a Problem-Reporting-Form (PRF), which comes
with every distribution and it helps us to trace the problems.

curl-loader is developed also at x86_64 Debian (lenny) 64-bit with Intel
quad-core HW.

What happens, if you remove the strings starting with # (comments)?
Which locality, etc settings do you have, which compiler, etc questions from
the PRF?

I would suspect, that the following testing from parse_conf.c somehow
goes screwed in your settings:

 /* Line may be commented out by '#'.*/
if (fgets_buff[0] == '#')
{
   // fprintf (stderr, "%s - skipping commented file string \"%s\n",
   //         __func__, fgets_buff);
   continue;
}


-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................