• Hello Klaus,


    I'm Experiencing an issue with "kprotectcl" Binary on Linux CentOS 6.

    It Throughs the following error:

    "Segmentation Fault (Core Dumped)".

    and the dmesg (linux debugging) shows the following line:

    kprotectcl[4993] general protection ip:405265 sp:7fffdb0774a0 error:0 in kprotectcl[400000+34000]

    The admins say that i need to contact the Developer, because the kprotect are using system wide Libraries.


    Could you please Help

  • Hello Klause,


    Here's more details about the issue, basically it says "Cannot allocate memory":

    14:05:59 open("/var/www/tours/", O_RDONLY) = 3
    14:05:59 fstat(3, {st_dev=makedev(8, 8), st_ino=16915657, st_mode=S_IFDIR|0777, st_nlink=10, st_uid=674, st_gid=674, st_blksize=4096, st_blocks=8, st_size=4096, st_atime=2013/02/23-16:04:55, st_mtime=2013/02/21-15:09:13, st_ctime=2013/02/21-17:54:45}) = 0
    14:05:59 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f612e469000
    14:05:59 fstat(3, {st_dev=makedev(8, 8), st_ino=16915657, st_mode=S_IFDIR|0777, st_nlink=10, st_uid=674, st_gid=674, st_blksize=4096, st_blocks=8, st_size=4096, st_atime=2013/02/23-16:04:55, st_mtime=2013/02/21-15:09:13, st_ctime=2013/02/21-17:54:45}) = 0
    14:05:59 lseek(3, 0, SEEK_END) = 9223372036854775807
    14:05:59 lseek(3, 0, SEEK_SET) = 0
    14:05:59 mmap(NULL, 9223372036854779904, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 ENOMEM (Cannot allocate memory)
    14:05:59 mmap(NULL, 9223372036854910976, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 ENOMEM (Cannot allocate memory)
    14:05:59 mmap(NULL, 134217728, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = 0x7f612645e000
    14:05:59 munmap(0x7f612645e000, 28975104) = 0
    14:05:59 munmap(0x7f612c000000, 38133760) = 0
    14:05:59 mprotect(0x7f6128000000, 135168, PROT_READ|PROT_WRITE) = 0
    14:05:59 mmap(NULL, 9223372036854779904, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 ENOMEM (Cannot allocate memory)
    14:05:59 read(3, 0, 9223372036854771712) = -1 EFAULT (Bad address)
    14:05:59 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
    14:06:00 +++ killed by SIGSEGV (core dumped) +++


    Could you please check this issue in your "kprotect" Code.

    Thanks

  • Hi,

    this here is the reason for the error:

    Code
    14:05:59 lseek(3, 0, SEEK_END) = 9223372036854775807

    That means that the seeking to the end of the file to get the file size is not possible for some reason.
    Instead of reporting the real file size, the wrong value 9223372036854775807 will be reported.
    In the next step the tools tries to allocate memory for the file, but because of the wrong and much too big value, this will fail.

    I have added now a check for the next version to detect this error-case and report a correct error message.
    But this will not solve your problem of course - there must be something wrong with the given file or there is a system related problem, but such problems can't be fixed from the tool.

    Best regards,
    Klaus

  • Ok, log understood, but what do you think the problem is.

    I need to at least point where the problem is, because the Admins are saying that the problem is with the code, and if you give me maybe some possibilities, or suggestions, so that the admins could check and maybe solve the problem (hopefully).


    Thanks

  • Ok, first of all, i'm using filelist, instead of only one file.

    But interestingly enough, when i swapped the -filelist with the actual files (one in each comand line), it went fine.

    I thought the files were big, but it turned out they're only 320KB.

    Note that all files have 777 permissions (read, write, Execute) for all.

    Strange huh?

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!