From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Yao Qi <yao@codesourcery.com>
Subject: Re: [patch] Fix leak of bp_jit_event breakpoints
Date: Wed, 26 Jan 2011 19:48:00 -0000 [thread overview]
Message-ID: <AANLkTimEzZHEXVMeg8mJFT3Fa=GN6nxF2y=VwWM5BDtn@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikLk0CxeXwMNDiOcQMds=GuXJb6FV2fD++HLevu@mail.gmail.com>
On Thu, Jan 20, 2011 at 3:27 PM, Paul Pluzhnikov <ppluzhnikov@google.com> wrote:
> That appears to work reasonably well.
>
> It fixes both the gdbserver failure in jit.exp, and also as yet undiscovered
> problem: the old static/global jit_descriptor_addr couldn't possibly work
> for more than one inferior.
Ping?
--
Paul Pluzhnikov
next prev parent reply other threads:[~2011-01-26 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 20:49 Paul Pluzhnikov
2011-01-19 21:14 ` Pedro Alves
2011-01-20 7:17 ` Paul Pluzhnikov
2011-01-21 1:11 ` Paul Pluzhnikov
2011-01-26 19:48 ` Paul Pluzhnikov [this message]
2011-01-27 14:15 ` Pedro Alves
2011-01-27 22:59 ` Paul Pluzhnikov
2011-01-28 1:27 ` Pedro Alves
2011-01-28 18:02 ` Paul Pluzhnikov
2011-01-28 20:38 ` Pedro Alves
2011-01-31 22:00 ` Paul Pluzhnikov
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='AANLkTimEzZHEXVMeg8mJFT3Fa=GN6nxF2y=VwWM5BDtn@mail.gmail.com' \
--to=ppluzhnikov@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=yao@codesourcery.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