public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sphink at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/13431] jit code registration cleanup Date: Fri, 16 Dec 2011 20:01:00 -0000 [thread overview] Message-ID: <bug-13431-4717-eeb3cwOXOp@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13431-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13431 --- Comment #2 from Steve Fink <sphink at gmail dot com> 2011-12-16 20:01:06 UTC --- Note that I've found this to be a serious usability issue. I control whether the JIT code registration does anything with an environment variable, but that doesn't help with this bug -- as long as __jit_debug_descriptor is defined in any linked object file, you'll occasionally get this problem. In my experience, it isn't even necessary to modify the file containing the __jit_debug_descriptor definition (or its headers) in order for it to be moved around. (Probably the linker is putting the object file at a different address or something.) And yet, you'll sometimes get lucky and recompile with major modifications without seeing this issue. -- 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.
next prev parent reply other threads:[~2011-12-16 20:01 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-22 21:31 [Bug gdb/13431] New: " sphink at gmail dot com 2011-12-16 19:56 ` [Bug gdb/13431] " sphink at gmail dot com 2011-12-16 20:01 ` sphink at gmail dot com [this message] 2012-02-01 17:45 ` tromey at redhat dot com 2012-02-01 20:22 ` cvs-commit at gcc dot gnu.org 2012-02-01 20:23 ` tromey at redhat dot com 2012-02-09 20:24 ` sphink at gmail dot com 2012-02-16 0:56 ` sphink at gmail dot com 2012-02-16 18:17 ` tromey at redhat dot com
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-13431-4717-eeb3cwOXOp@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).