From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: sanjoy@playingwithpointers.com
Cc: gdb-patches@sourceware.org, sanjoy@playingwithpointers.com
Subject: Re: [PATCH 4/4] Activate JIT code unwinder for i386.
Date: Tue, 05 Jul 2011 15:34:00 -0000 [thread overview]
Message-ID: <201107051524.p65FO8pL010651@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <1309847489-13760-4-git-send-email-sanjoy@playingwithpointers.com> (message from Sanjoy Das on Tue, 5 Jul 2011 12:01:29 +0530)
> From: Sanjoy Das <sanjoy@playingwithpointers.com>
> Date: Tue, 5 Jul 2011 12:01:29 +0530
>
> Registers the (pseudo) unwinder for JIT code for i386. This can
> probably be expanded to other architectures after some testing and
> review.
What's your motivation for putting the JIT unwinder at that spot in
the list of unwinders? I'd put it behind the DWARF CFI unwinders
since those are the ones that most people will hit.
> gdb/ChangeLog:
> * i386-tdep.c: Activate JIT unwinder for i386.
> ---
> gdb/ChangeLog | 4 ++++
> gdb/i386-tdep.c | 4 ++++
> 2 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
> index 306a0a5..1f0bd19 100644
> --- a/gdb/ChangeLog
> +++ b/gdb/ChangeLog
> @@ -1,5 +1,9 @@
> 2011-07-04 Sanjoy Das <sanjoy@playingwithpointers.com>
>
> + * i386-tdep.c: Activate JIT unwinder for i386.
> +
> +2011-07-04 Sanjoy Das <sanjoy@playingwithpointers.com>
> +
> * jit.c: Add JIT frame unwinding code.
> * jit-reader.h: Added jit_prepend_unwinder.
>
> diff --git a/gdb/i386-tdep.c b/gdb/i386-tdep.c
> index 366d0fa..66626ab 100644
> --- a/gdb/i386-tdep.c
> +++ b/gdb/i386-tdep.c
> @@ -30,6 +30,7 @@
> #include "frame-base.h"
> #include "frame-unwind.h"
> #include "inferior.h"
> +#include "jit.h"
> #include "gdbcmd.h"
> #include "gdbcore.h"
> #include "gdbtypes.h"
> @@ -7330,6 +7331,9 @@ i386_gdbarch_init (struct gdbarch_info info, struct gdbarch_list *arches)
> CFI info will be used if it is available. */
> dwarf2_append_unwinders (gdbarch);
>
> + /* JIT reader pseudo-unwinder. */
> + jit_prepend_unwinder (gdbarch);
> +
> frame_base_set_default (gdbarch, &i386_frame_base);
>
> /* Pseudo registers may be changed by amd64_init_abi. */
> --
> 1.7.5.3
>
>
next prev parent reply other threads:[~2011-07-05 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 6:27 [PATCH 1/4] jit-reader.h: describe interface implemented by the JIT readers Sanjoy Das
2011-07-05 6:27 ` [PATCH 4/4] Activate JIT code unwinder for i386 Sanjoy Das
2011-07-05 15:34 ` Mark Kettenis [this message]
2011-07-06 2:38 ` Sanjoy Das
2011-07-06 2:46 ` Mark Kettenis
2011-07-05 6:27 ` [PATCH 2/4] Add symbol-handling callbacks to the jit-reader interface Sanjoy Das
2011-07-05 7:53 ` [PATCH 3/4] Add an unwinder for JIT compiled code Sanjoy Das
2011-07-05 16:15 ` [PATCH 1/4] jit-reader.h: describe interface implemented by the JIT readers Yao Qi
2011-07-13 20:24 Sanjoy Das
2011-07-13 20:24 ` [PATCH 4/4] Activate JIT code unwinder for i386 Sanjoy Das
2011-07-14 17:55 ` Tom Tromey
2011-07-14 17:58 ` 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=201107051524.p65FO8pL010651@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--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