public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "neleai at seznam dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug malloc/15592] mtrace.c tr_break() is not called from malloc hooks Date: Mon, 14 Oct 2013 16:08:00 -0000 [thread overview] Message-ID: <bug-15592-131-i2fqirwYGc@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15592-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15592 Ondrej Bilka <neleai at seznam dot cz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |neleai at seznam dot cz --- Comment #1 from Ondrej Bilka <neleai at seznam dot cz> --- Created attachment 7233 --> https://sourceware.org/bugzilla/attachment.cgi?id=7233&action=edit patch Does marking tr_break noinline help? What about second trick of adding side effect as a __asm__ in attached patch does? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-14 16:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-06 16:53 [Bug malloc/15592] New: " fcollyer at gmail dot com 2013-10-14 16:08 ` neleai at seznam dot cz [this message] 2014-01-04 23:20 ` [Bug malloc/15592] " fcollyer at gmail dot com 2014-06-13 15:09 ` fweimer at redhat dot com 2021-07-14 2:50 ` siddhesh at sourceware dot 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-15592-131-i2fqirwYGc@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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).