From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: sanjoy@playingwithpointers.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4] Activate JIT code unwinder for i386.
Date: Wed, 06 Jul 2011 02:46:00 -0000 [thread overview]
Message-ID: <201107060238.p662cDaG005037@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <CAMiUf7eeqjufkCmmLiZVYG_b7yb15j0D6BLkWbc83C3atszT4Q@mail.gmail.com> (message from Sanjoy Das on Wed, 6 Jul 2011 08:01:34 +0530)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
> From: Sanjoy Das <sanjoy@playingwithpointers.com>
> Date: Wed, 6 Jul 2011 08:01:34 +0530
>
> > 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.
> >
>
> I'll fix that before the next iteration.
Well, if you have a good reason to prepend it, that's ok. But if not,
then yes, I think it's the way to go.
next prev parent reply other threads:[~2011-07-06 2:38 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 2/4] Add symbol-handling callbacks to the jit-reader interface 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
2011-07-06 2:38 ` Sanjoy Das
2011-07-06 2:46 ` Mark Kettenis [this message]
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=201107060238.p662cDaG005037@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