public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libmudflap/51858] New: Some malloc'd inside libc is not being tracked
Date: Sat, 14 Jan 2012 07:12:00 -0000 [thread overview]
Message-ID: <bug-51858-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51858
Bug #: 51858
Summary: Some malloc'd inside libc is not being tracked
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libmudflap
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: pinskia@gcc.gnu.org
On mips64-linux-gnu with our compiled glibc, we get many failures in libmudflap
testsuite.
The backtrace for those are failures is:
#0 __lll_lock_wait_private (futex=0x2ad84960) at
../nptl/sysdeps/unix/sysv/linux/lowlevellock.c:33
#1 0x2ad41380 in _Unwind_Find_registered_FDE (pc=0x2adf41b7, bases=0x7ffdf1e8)
at ../sysdeps/generic/unwind-dw2-fde.c:1011
#2 0x2ad413bc in _Unwind_Find_FDE (pc=0x2adf41b7, bases=0x7ffdf1e8) at
../sysdeps/generic/unwind-dw2-fde-glibc.c:257
#3 0x2adf2b24 in uw_frame_state_for (context=context@entry=0x7ffdeee8,
fs=fs@entry=0x7ffdd680) at
/home/apinski/src/gcc-fsf/local/gcc/libgcc/unwind-dw2.c:1179
#4 0x2adf30b0 in uw_init_context_1 (context=context@entry=0x7ffdeee8,
outer_cfa=outer_cfa@entry=0x7ffdf330, outer_ra=0x2ad1377c,
outer_ra@entry=0x2adf41b8)
at /home/apinski/src/gcc-fsf/local/gcc/libgcc/unwind-dw2.c:1500
#5 0x2adf41b8 in _Unwind_Backtrace (trace=0x2ad135c0 <backtrace_helper>,
trace_argument=0x7ffdf330) at
/home/apinski/src/gcc-fsf/local/gcc/libgcc/unwind.inc:283
#6 0x2ad1377c in __GI___backtrace (array=<optimized out>, size=6) at
../sysdeps/ia64/backtrace.c:85
#7 0x2aae591c in __mf_backtrace (symbols=0x7ffdf448, guess_pc=0x2aae7918,
guess_omit_levels=2) at
/home/apinski/src/gcc-fsf/local/gcc/libmudflap/mf-runtime.c:1981
#8 0x2aae7088 in __mf_violation (ptr=0x100a1338, sz=0, pc=716077336,
location=<optimized out>, type=4)
at /home/apinski/src/gcc-fsf/local/gcc/libmudflap/mf-runtime.c:2106
#9 0x2aae74a4 in __mfu_unregister (ptr=0x100a1338, sz=0, type=<optimized out>)
at /home/apinski/src/gcc-fsf/local/gcc/libmudflap/mf-runtime.c:1351
#10 0x2aae7918 in __mf_unregister (ptr=0x100a1338, sz=0, type=2) at
/home/apinski/src/gcc-fsf/local/gcc/libmudflap/mf-runtime.c:1291
#11 0x2aae95c4 in free (buf=0x100a1338) at
/home/apinski/src/gcc-fsf/local/gcc/libmudflap/mf-hooks1.c:268
#12 0x2ad40f10 in __deregister_frame_info_bases (begin=0x2ac04ebc) at
../sysdeps/generic/unwind-dw2-fde.c:227
#13 0x2abf4164 in _ftext () from /lib32/octeon2/libpthread.so.0
#14 0x2ac03ebc in _fini () from /lib32/octeon2/libpthread.so.0
#15 0x2aabfb20 in _dl_fini () at dl-fini.c:248
#16 0x2ac53f70 in __GI_exit (status=0) at exit.c:75
#17 0x2ac38ba8 in __libc_start_main (main=0x10000a30 <__wrap_main@plt>, argc=1,
ubp_av=0x7ffdf804, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>,
stack_end=<optimized out>) at libc-start.c:252
#18 0x10001020 in __start ()
--- CUT ---
__deregister_frame_info_bases has uses a mutex which is also used from
_Unwind_Find_registered_FDE which is what is causing the infinite loop.
Though we should not have an unregisterd memory location here though.
next reply other threads:[~2012-01-14 3:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 7:12 pinskia at gcc dot gnu.org [this message]
2013-11-10 5:53 ` [Bug libmudflap/51858] " pinskia at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-51858-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).