Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>, Yao Qi <yao@codesourcery.com>
Subject: Re: [patch] Add tests for JIT debugging interface
Date: Wed, 19 Jan 2011 21:04:00 -0000	[thread overview]
Message-ID: <201101191349.16542.pedro@codesourcery.com> (raw)
In-Reply-To: <AANLkTi=rBc_piQtpJ5uUO4ObaMGn=PKq3L8LmUnU+fHs@mail.gmail.com>

On Wednesday 19 January 2011 12:26:34, Paul Pluzhnikov wrote:
> On Wed, Jan 19, 2011 at 11:03 AM, Pedro Alves <pedro@codesourcery.com> 

> > It's output from infrun.c:normal_stop.  Sounds like a bug somewhere.
> 
> It is a bug. Fix in progress...
> 
> >> That's alright -- I was going to fix this area (see "JIT interface
> >> slowness" in gdb@sourceware.org list), and this isn't the only problem
> >> -- I also noticed that we leak several jit_breakpoints on rerun.
> 
> That leak is in fact causing the bug above ...

Ah.

Patch is okay.  As general principle, I'd rather fix the leak first and
avoid introducing new failures against gdbserver if possible and
easy, but if you want to check this in already, that'll  be okay too.

-- 
Pedro Alves


  reply	other threads:[~2011-01-19 20:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 23:28 Paul Pluzhnikov
2011-01-12  7:02 ` Yao Qi
2011-01-12 10:44   ` Pedro Alves
2011-01-12 15:19     ` Paul Pluzhnikov
2011-01-12 16:12       ` Pedro Alves
2011-01-12 17:23       ` Yao Qi
2011-01-12 17:33         ` Paul Pluzhnikov
2011-01-18 17:07           ` Paul Pluzhnikov
2011-01-19 19:27           ` Pedro Alves
2011-01-19 20:30             ` Paul Pluzhnikov
2011-01-19 21:04               ` Pedro Alves [this message]
2011-01-19 21:09               ` Yao Qi
2011-01-12 10:03 ` 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=201101191349.16542.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ppluzhnikov@google.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