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/18057] New: no way for a jit frame id to fail Date: Fri, 27 Feb 2015 23:05:00 -0000 [thread overview] Message-ID: <bug-18057-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=18057 Bug ID: 18057 Summary: no way for a jit frame id to fail 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 the jit get_frame_id callback must always succeed. However this is a bit of a pain because it may need to make calls into gdb which could fail. Currently I'm just ignoring any such possible error, but I think a better API might be to unify the unwind and get_frame_id methods, requiring unwind to compute a frame id if it succeeds. -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2015-02-27 23:03 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-18057-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: 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).