From: Alexander Smundak <asmundak@google.com>
To: Andy Wingo <wingo@igalia.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: Thu, 26 Feb 2015 21:50:00 -0000 [thread overview]
Message-ID: <CAHQ51u7VDSHyfDc7Zt3d4J0fbgPg23LqtdwrRuSzSz6bMPHSdA@mail.gmail.com> (raw)
In-Reply-To: <871tlcq1in.fsf@igalia.com>
My GDB repository is internal, sorry. I still hope my patch will be
reviewed soon :-)
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.
Regards
Alexander
On Thu, Feb 26, 2015 at 4:51 AM, Andy Wingo <wingo@igalia.com> wrote:
> On Thu 26 Feb 2015 12:49, Pedro Alves <palves@redhat.com> writes:
>
>> On 02/26/2015 08:58 AM, Andy Wingo wrote:
>>
>>> Who are the right people? I'm happy to do work off and on around these things, if
>>> you are interested.
>>
>> Looks like you could be coordinating your ideas with
>> Alexander Smundak (added to CC), which is wanting similar
>> things for OpenJDK:
>>
>> https://sourceware.org/ml/gdb-patches/2015-02/msg00735.html
>>
>> Alexander, this thread is here:
>>
>> https://sourceware.org/ml/gdb-patches/2015-02/msg00739.html
>
> Oh neat. That approach looks more aligned to V8's needs. I will see if
> I can cook up a patch based on Alexander's work that does the same thing
> in Guile and write an unwinder for V8. I will let you know when I have
> this done. Of course I do not intend to block Alexander's work in any
> way, but perhaps this could provide additional feedback about the use
> case.
>
> Alexander do you have your work in a git repository anywhere? It might
> be easier to coordinate, if that's a thing you are interested in, and to
> track changes in your work as you react to Doug et al's feedback. I
> sometimes sync up to this tree, FWIW:
>
> https://github.com/andywingo/binutils-gdb/commits/master
>
> Regards,
>
> Andy
next prev parent reply other threads:[~2015-02-26 21:50 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 [this message]
2015-02-27 12:59 ` Andy Wingo
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=CAHQ51u7VDSHyfDc7Zt3d4J0fbgPg23LqtdwrRuSzSz6bMPHSdA@mail.gmail.com \
--to=asmundak@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=wingo@igalia.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