From: Tom Tromey <tromey@redhat.com>
To: Sanjoy Das <sanjoy@playingwithpointers.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 6/7] New JIT unwinder.
Date: Tue, 30 Aug 2011 19:28:00 -0000 [thread overview]
Message-ID: <m3obz6aedh.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1314518609-10204-7-git-send-email-sanjoy@playingwithpointers.com> (Sanjoy Das's message of "Sun, 28 Aug 2011 13:33:28 +0530")
>>>>> "Sanjoy" == Sanjoy Das <sanjoy@playingwithpointers.com> writes:
Sanjoy> Introduce a "proxy unwinder", whcih will pass down all calls to the
Sanjoy> functions the JIT reader provides.
Sanjoy> + value->free = (void (*) (struct gdb_reg_value *)) xfree;
I think either the free function's type should be changed, or you should
go back to the previous version here. Function casts are bad, we should
avoid them as much as possible. My preference is for the previous patch
as I think the earlier critique was mistaken, but I am ok with either
approach.
Sanjoy> +static enum unwind_stop_reason
Sanjoy> +jit_frame_unwind_stop_reason (struct frame_info *this_frame, void **cache)
Sanjoy> +{
Sanjoy> + return default_frame_unwind_stop_reason (this_frame, cache);
Sanjoy> +}
I think you can just delete this function and put
default_frame_unwind_stop_reason directly into jit_frame_unwind.
Otherwise this looks good to me.
Tom
next prev parent reply other threads:[~2011-08-30 19:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 13:08 JIT Debug Info Reader Sanjoy Das
2011-08-27 13:08 ` [PATCH 6/7] New JIT unwinder Sanjoy Das
2011-08-28 2:17 ` Sergio Durigan Junior
[not found] ` <1314518609-10204-1-git-send-email-sanjoy@playingwithpointers.com>
2011-08-28 8:04 ` [PATCH 7/7] Documentation Sanjoy Das
2011-08-30 19:43 ` Tom Tromey
2011-08-28 8:04 ` [PATCH 5/7] Use the loaded reader Sanjoy Das
2011-08-30 19:18 ` Tom Tromey
2011-08-28 8:04 ` [PATCH 4/7] New commands for loading and unloading a reader Sanjoy Das
2011-08-30 18:52 ` Tom Tromey
2011-08-28 8:04 ` [PATCH 3/7] Platform agnostic dynamic loading code Sanjoy Das
2011-08-28 8:04 ` [PATCH 6/7] New JIT unwinder Sanjoy Das
2011-08-30 19:28 ` Tom Tromey [this message]
2011-08-28 8:05 ` [PATCH 2/7] Relocatable directory for loading JIT readers Sanjoy Das
2011-08-30 18:32 ` Tom Tromey
2011-08-28 8:07 ` [PATCH 1/7] Introduce jit-reader.in and modify build system Sanjoy Das
2011-08-30 18:30 ` Tom Tromey
2011-08-31 3:16 ` Sanjoy Das
2011-08-31 17:44 ` Tom Tromey
2011-08-27 13:08 ` [PATCH 4/7] New commands for loading and unloading a reader Sanjoy Das
2011-08-27 14:51 ` Abhijit Halder
2011-08-27 13:08 ` [PATCH 2/7] Relocatable directory for loading JIT readers Sanjoy Das
2011-08-27 13:08 ` [PATCH 3/7] Platform agnostic dynamic loading code Sanjoy Das
2011-08-27 13:08 ` [PATCH 5/7] Use the loaded reader Sanjoy Das
2011-08-27 13:47 ` Abhijit Halder
2011-08-27 14:18 ` Abhijit Halder
2011-08-27 13:08 ` [PATCH 1/7] Introduce jit-reader.in and modify build system Sanjoy Das
2011-08-27 13:08 ` [PATCH 7/7] Documentation Sanjoy Das
-- strict thread matches above, loose matches on Subject: below --
2011-08-31 3:31 JIT Reader (re-roll) Sanjoy Das
2011-08-31 3:32 ` [PATCH 6/7] New JIT unwinder Sanjoy Das
2011-08-24 18:57 JIT Debug Info Reader (re-roll) Sanjoy Das
2011-08-24 18:57 ` [PATCH 6/7] New JIT unwinder Sanjoy Das
2011-08-24 19:04 ` Jan Kratochvil
2011-08-24 19:08 ` Sanjoy Das
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=m3obz6aedh.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sanjoy@playingwithpointers.com \
/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