This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/14359] tst-cancelx4.out: Segmentation fault
- From: "wbrana at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Sat, 14 Jul 2012 09:07:50 +0000
- Subject: [Bug libc/14359] tst-cancelx4.out: Segmentation fault
- Auto-submitted: auto-generated
- References: <bug-14359-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14359
--- Comment #11 from wbrana at gmail dot com 2012-07-14 09:07:50 UTC ---
==22761== Thread 2:
==22761== Invalid read of size 4
==22761== at 0x109AC0: ??? (in
/mnt/md3/cache/portage/sys-libs/glibc-2.16.0/work/build-x86-x86_64-pc-linux-gnu-nptl/nptl/tst-cancelx4)
==22761== by 0x493F4ED: clone (in /lib32/libc-2.14.1.so)
==22761== Address 0x170 is not stack'd, malloc'd or (recently) free'd
==22761==
==22761==
==22761== Process terminating with default action of signal 11 (SIGSEGV)
==22761== Access not within mapped region at address 0x170
==22761== at 0x109AC0: ??? (in
/mnt/md3/cache/portage/sys-libs/glibc-2.16.0/work/build-x86-x86_64-pc-linux-gnu-nptl/nptl/tst-cancelx4)
==22761== by 0x493F4ED: clone (in /lib32/libc-2.14.1.so)
==22761== If you believe this happened as a result of a stack
==22761== overflow in your program's main thread (unlikely but
==22761== possible), you can try to increase the size of the
==22761== main thread stack using the --main-stacksize= flag.
==22761== The main thread stack size used in this run was 8388608.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.