From: Pedro Alves <palves@redhat.com>
To: Yichao Yu <yyc1992@gmail.com>
Cc: gdb@sourceware.org, Paul Pluzhnikov <ppluzhnikov@google.com>
Subject: Re: JIT debugging (Attach and speed)
Date: Wed, 23 Mar 2016 12:24:00 -0000 [thread overview]
Message-ID: <56F28B17.4060508@redhat.com> (raw)
In-Reply-To: <CAMvDr+ST=4a11-B=ymUQDRdOCZmVUgdfkhFbUDknvjkaGjtGWw@mail.gmail.com>
On 03/23/2016 02:18 AM, Yichao Yu wrote:
>> It'd be very nice if we had a _new_ test that covers your use case,
>> to avoid regressing again. That likely makes the patch bigger than
>> what we could accept without a copyright assignment though. If you'd
>> like to pursue that, let me know and I'll send you the forms.
>
> I've got a simple patch that fixes the issue for me and AFAICT all of
> the failing tests are racy and/or failing on this machine before the
> change too. I haven't add test yet since I'm not so sure how to add it
> (I found test for both jit interface and attach but haven't figured
> out how to write a new one yet...).
Excellent, this helps a lot.
I have an idea for the test, so I'll handle it. Let me bundle
things in a proper patch and post it to gdb-patches. Stay tuned.
>
> I'm happy to complete copyright related forms necessary.
I'll send this off list.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-03-23 12:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 14:56 Yichao Yu
2016-03-22 15:46 ` Pedro Alves
2016-03-22 16:10 ` Paul Pluzhnikov
2016-03-22 16:15 ` Pedro Alves
2016-03-22 16:23 ` Yichao Yu
2016-03-22 16:41 ` Pedro Alves
2016-03-22 16:47 ` Yichao Yu
2016-03-22 17:00 ` Pedro Alves
2016-03-23 2:18 ` Yichao Yu
2016-03-23 4:51 ` Yichao Yu
2016-03-23 18:24 ` Pedro Alves
2016-03-23 19:32 ` Yichao Yu
2016-03-23 19:48 ` Pedro Alves
2016-03-23 20:51 ` Yichao Yu
2016-03-24 1:17 ` Pedro Alves
2016-03-24 3:14 ` Yichao Yu
2016-03-24 21:02 ` Yichao Yu
2016-03-23 12:24 ` Pedro Alves [this message]
2016-03-23 13:31 ` Pedro Alves
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=56F28B17.4060508@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.com \
--cc=yyc1992@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