Menu

#2320 SEGV on unknown address

None
closed-fixed
nobody
None
2020-09-27
2020-09-25
No

gnuplot 5.5 in centos linux 7.7.1908

==8622== ERROR: AddressSanitizer: SEGV on unknown address 0x7ffe13d95000 (pc 0x7f2c873ba285 sp 0x7ffe13d8e3f0 bp 0x7ffe13d8f2f0 T0)

AddressSanitizer can not provide additional info.

#0 0x7f2c873ba284 (/usr/lib64/libc-2.17.so+0x4a284)

#1 0x7f2c873bde5a (/usr/lib64/libc-2.17.so+0x4de5a)

#2 0x7f2c873b881d (/usr/lib64/libc-2.17.so+0x4881d)

#3 0x92976f (/root/bug_finder/target_program/asan_program/gnuplot+0x92976f)

#4 0x4af409 (/root/bug_finder/target_program/asan_program/gnuplot+0x4af409)

#5 0x6894db (/root/bug_finder/target_program/asan_program/gnuplot+0x6894db)

#6 0x463bc3 (/root/bug_finder/target_program/asan_program/gnuplot+0x463bc3)

#7 0x459f6c (/root/bug_finder/target_program/asan_program/gnuplot+0x459f6c)

#8 0x61b63b (/root/bug_finder/target_program/asan_program/gnuplot+0x61b63b)

#9 0x40772e (/root/bug_finder/target_program/asan_program/gnuplot+0x40772e)

#10 0x7f2c87392554 (/usr/lib64/libc-2.17.so+0x22554)

#11 0x4084ec (/root/bug_finder/target_program/asan_program/gnuplot+0x4084ec)

==8622== ABORTING

1 Attachments

Discussion

  • liuchenyifan

    liuchenyifan - 2020-09-25

    information below from valgrind

    "./crash/bug1" line 1: warning: ==2264== Invalid read of size 4
    ==2264== at 0x61512ED: vfprintf (in /usr/lib64/libc-2.17.so)
    ==2264== by 0x6154E5A: buffered_vfprintf (in /usr/lib64/libc-2.17.so)
    ==2264== by 0x614F81D: vfprintf (in /usr/lib64/libc-2.17.so)
    ==2264== by 0x82F69D: int_warn (util.c:1225)
    ==2264== by 0x498892: df_open (datafile.c:1438)
    ==2264== by 0x61ABBF: eval_plots (plot2d.c:2218)
    ==2264== by 0x44BB88: plot_command (command.c:1897)
    ==2264== by 0x4411AB: command (command.c:659)
    ==2264== by 0x4411AB: do_line (command.c:429)
    ==2264== by 0x5CD14B: load_file (misc.c:335)
    ==2264== by 0x406416: main (plot.c:636)
    ==2264== Address 0x1fff001000 is not stack'd, malloc'd or (recently) free'd
    ==2264==
    ==2264==
    ==2264== Process terminating with default action of signal 11 (SIGSEGV)
    ==2264== Access not within mapped region at address 0x1FFF001000
    ==2264== at 0x61512ED: vfprintf (in /usr/lib64/libc-2.17.so)
    ==2264== by 0x6154E5A: buffered_vfprintf (in /usr/lib64/libc-2.17.so)
    ==2264== by 0x614F81D: vfprintf (in /usr/lib64/libc-2.17.so)
    ==2264== by 0x82F69D: int_warn (util.c:1225)
    ==2264== by 0x498892: df_open (datafile.c:1438)
    ==2264== by 0x61ABBF: eval_plots (plot2d.c:2218)
    ==2264== by 0x44BB88: plot_command (command.c:1897)
    ==2264== by 0x4411AB: command (command.c:659)
    ==2264== by 0x4411AB: do_line (command.c:429)
    ==2264== by 0x5CD14B: load_file (misc.c:335)
    ==2264== by 0x406416: main (plot.c:636)
    ==2264== If you believe this happened as a result of a stack
    ==2264== overflow in your program's main thread (unlikely but
    ==2264== possible), you can try to increase the size of the
    ==2264== main thread stack using the --main-stacksize= flag.
    ==2264== The main thread stack size used in this run was 8388608.
    ==2264==
    ==2264== HEAP SUMMARY:
    ==2264== in use at exit: 1,367,752 bytes in 172 blocks
    ==2264== total heap usage: 281 allocs, 109 frees, 1,499,580 bytes allocated
    ==2264==
    ==2264== LEAK SUMMARY:
    ==2264== definitely lost: 0 bytes in 0 blocks
    ==2264== indirectly lost: 0 bytes in 0 blocks
    ==2264== possibly lost: 0 bytes in 0 blocks
    ==2264== still reachable: 1,367,752 bytes in 172 blocks
    ==2264== suppressed: 0 bytes in 0 blocks
    ==2264== Rerun with --leak-check=full to see details of leaked memory
    ==2264==
    ==2264== For lists of detected and suppressed errors, rerun with: -s
    ==2264== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

     
  • Ethan Merritt

    Ethan Merritt - 2020-09-27
    • status: open --> closed-fixed
    • Group: -->
    • Priority: -->
     
  • Ethan Merritt

    Ethan Merritt - 2020-09-27

    sanitizing error introduced by commit b94024a80a
    now fixed

     

Log in to post a comment.