This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[Bug backtrace/18057] New: no way for a jit frame id to fail

From: "tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
To: gdb-prs at sourceware dot org
Date: Fri, 27 Feb 2015 23:03:13 +0000
Subject: [Bug backtrace/18057] New: no way for a jit frame id to fail
Auto-submitted: auto-generated

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.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]