public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/18058] New: provide jit api with some control over sniffer priority
Date: Fri, 27 Feb 2015 23:15:00 -0000	[thread overview]
Message-ID: <bug-18058-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 18058
           Summary: provide jit api with some control over sniffer
                    priority
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: backtrace
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at sourceware dot org

Currently I think the JIT frame unwinder is given a fairly
high priority:

      frame_unwind_prepend_unwinder (gdbarch, &jit_frame_unwind);

In my case, I think the resulting sniffer will necessarily have
to use a heuristic to decide if it is looking at a JIT frame.
So, it would be nice to be able to specify that this unwinder
should come after any sniffer that works off the debug info,
as those are probably more reliable.

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


                 reply	other threads:[~2015-02-27 23:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-18058-4717@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: 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).