[Bug libc/18333] New: FAIL: timezone/tst-tzset (segmentation fault)

["hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=18333

            Bug ID: 18333
           Summary: FAIL: timezone/tst-tzset (segmentation fault)
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: hjl.tools at gmail dot com
                CC: drepper.fsp at gmail dot com, fweimer at redhat dot com
  Target Milestone: ---

On x32, I got

(gdb) r --direct
Starting program:
/export/build/gnu/glibc-x32/build-x86_64-linux/timezone/tst-tzset --direct

Program received signal SIGSEGV, Segmentation fault.
0xf7a95a23 in _int_free (av=<optimized out>, p=<optimized out>, have_lock=0)
    at malloc.c:3979
3979            unlink(nextchunk, bck, fwd);
(gdb) bt
#0  0xf7a95a23 in _int_free (av=<optimized out>, p=<optimized out>, 
    have_lock=0) at malloc.c:3979
#1  0xf7a9a2cb in __GI___libc_free (mem=<optimized out>) at malloc.c:2949
#2  0xf7a840a8 in _IO_new_fclose (fp=<optimized out>) at iofclose.c:85
#3  0xf7ad3213 in __tzfile_read (file=<optimized out>, 
    file@entry=0x6042a3 "/tmp/tst-tzset-Jr2s0j", extra=extra@entry=0, 
    extrap=extrap@entry=0x0) at tzfile.c:450
#4  0xf7ad2299 in tzset_internal (explicit=1, always=1) at tzset.c:447
#5  __tzset () at tzset.c:600
#6  0x0040180b in test_tz_file (size=4294967290) at tst-tzset.c:108
#7  0x004019a4 in do_test () at tst-tzset.c:164
#8  0x004011fc in main (argc=<optimized out>, argv=<optimized out>)
    at ../test-skeleton.c:356
(gdb) 

On x86-64, I got

==22306== Memcheck, a memory error detector
==22306== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==22306== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==22306== Command: ./build-x86_64-linux/timezone/tst-tzset --direct
==22306== 
==22306== Invalid read of size 1
==22306==    at 0x4C2CB82: strlen (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==22306==    by 0x4EDEAEF: update_vars (tzset.c:161)
==22306==    by 0x4EDF1B8: __tzset_parse_tz (tzset.c:386)
==22306==    by 0x4EDF5E1: tzset (tzset.c:591)
==22306==    by 0x401F0D: do_test (tst-tzset.c:196)
==22306==    by 0x4016D6: main (test-skeleton.c:356)
==22306==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==22306== 
==22306== 
==22306== Process terminating with default action of signal 11 (SIGSEGV)
==22306==  Access not within mapped region at address 0x0
==22306==    at 0x4C2CB82: strlen (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==22306==    by 0x4EDEAEF: update_vars (tzset.c:161)
==22306==    by 0x4EDF1B8: __tzset_parse_tz (tzset.c:386)
==22306==    by 0x4EDF5E1: tzset (tzset.c:591)
==22306==    by 0x401F0D: do_test (tst-tzset.c:196)
==22306==    by 0x4016D6: main (test-skeleton.c:356)
==22306==  If you believe this happened as a result of a stack
==22306==  overflow in your program's main thread (unlikely but
==22306==  possible), you can try to increase the size of the
==22306==  main thread stack using the --main-stacksize= flag.
==22306==  The main thread stack size used in this run was 8388608.
==22306== 
==22306== HEAP SUMMARY:
==22306==     in use at exit: 67,108,929 bytes in 3 blocks
==22306==   total heap usage: 84 allocs, 81 frees, 559,940,347 bytes allocated
==22306== 
==22306== LEAK SUMMARY:
==22306==    definitely lost: 0 bytes in 0 blocks
==22306==    indirectly lost: 0 bytes in 0 blocks
==22306==      possibly lost: 0 bytes in 0 blocks
==22306==    still reachable: 67,108,929 bytes in 3 blocks
==22306==         suppressed: 0 bytes in 0 blocks
==22306== Rerun with --leak-check=full to see details of leaked memory
==22306== 
==22306== For counts of detected and suppressed errors, rerun with: -v
==22306== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
[1]    22306 segmentation fault (core dumped)  valgrind
./build-x86_64-linux/timezone/tst-tzset --direct

-- 
You are receiving this mail because:
You are on the CC list for the bug.