This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
With this patch:

diff --git a/timezone/tst-tzset.c b/timezone/tst-tzset.c
index aefcc76..4aff73c 100644
--- a/timezone/tst-tzset.c
+++ b/timezone/tst-tzset.c
@@ -184,7 +184,7 @@ do_test (void)
   return 1;
       }
     tzset ();
-
+#if 0
     memset (value, '0', length);
     value[0] = '<';
     value[length - 1] = '>';
@@ -194,6 +194,7 @@ do_test (void)
   return 1;
       }
     tzset ();
+#endif
   }

   return errors > 0;

I got

==20674== Memcheck, a memory error detector
==20674== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==20674== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==20674== Command: ./build-x86_64-linux/timezone/tst-tzset --direct
==20674== 
==20674== Syscall param unlink(pathname) points to unaddressable byte(s)
==20674==    at 0x4F11DD7: unlink (syscall-template.S:81)
==20674==    by 0x4E9B188: remove (remove.c:34)
==20674==    by 0x401B88: delete_temp_files (test-skeleton.c:102)
==20674==    by 0x4E6AEB1: __run_exit_handlers (exit.c:82)
==20674==    by 0x4E6AF04: exit (exit.c:104)
==20674==    by 0x4E558B6: (below main) (libc-start.c:323)
==20674==  Address 0x51d9450 is 0 bytes inside a block of size 22 free'd
==20674==    at 0x4C2ACE9: free (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==20674==    by 0x401E6F: do_test (tst-tzset.c:158)
==20674==    by 0x4016D6: main (test-skeleton.c:356)

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]