Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: Alexander Smundak <asmundak@google.com>
Cc: Pedro Alves <palves@redhat.com>,  Doug Evans <xdje42@gmail.com>,
	 gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] JIT read_debug_info callback takes target symfile addr
Date: Fri, 27 Feb 2015 12:59:00 -0000	[thread overview]
Message-ID: <877fv35x38.fsf@igalia.com> (raw)
In-Reply-To: <CAHQ51u7VDSHyfDc7Zt3d4J0fbgPg23LqtdwrRuSzSz6bMPHSdA@mail.gmail.com>	(Alexander Smundak's message of "Thu, 26 Feb 2015 13:50:15 -0800")

Hi,

On Thu 26 Feb 2015 22:50, Alexander Smundak <asmundak@google.com> writes:

> How set are you on implementing the unwinder for V8 in Guile rather
> than in Python? Having unwinders for different mixed language
> environment might help reveal API deficiencies sooner.

Which mix -- target or extension language?  I assume you refer to the
target (JS/V8 versus Java/OpenJDK).  In any case the API that Python and
Guile would expose would be very similar, so I would think that the
feedback on the API doesn't depend much on the extension language.

That said, as I get to choose, I choose Guile :)  My V8 debugging tools
are already in Guile, FWIW.

Andy


      reply	other threads:[~2015-02-27 12:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 14:16 Andy Wingo
2015-02-25 18:18 ` Doug Evans
2015-02-26  8:58   ` Andy Wingo
2015-02-26 11:50     ` Pedro Alves
2015-02-26 12:51       ` Andy Wingo
2015-02-26 21:50         ` Alexander Smundak
2015-02-27 12:59           ` Andy Wingo [this message]

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=877fv35x38.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=asmundak@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=xdje42@gmail.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