public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: gdb@sourceware.org, Xun Xun <xunxun1982@gmail.com>
Subject: Re: [mingw] gdb eat a lot of memory and slowly when start an inferior
Date: Fri, 27 Jan 2012 19:09:00 -0000	[thread overview]
Message-ID: <20120127190847.GQ31397@adacore.com> (raw)
In-Reply-To: <20120127153803.GP31397@adacore.com>

> Can you try the attached patch? This should restore the only effective
> change I made for non-Ada units.

Never mind. I think Jan found the source of the problem:
http://www.sourceware.org/ml/gdb-patches/2012-01/msg00953.html

-- 
Joel

  reply	other threads:[~2012-01-27 19:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 10:54 asmwarrior
2012-01-27 11:01 ` Joel Brobecker
2012-01-27 14:06   ` asmwarrior
     [not found]   ` <4F22AFF5.1000609@gmail.com>
2012-01-27 15:38     ` Joel Brobecker
2012-01-27 19:09       ` Joel Brobecker [this message]
2012-01-28  1:33         ` asmwarrior
2012-01-27 13:17 ` xunxun
2012-01-27 13:30   ` asmwarrior

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=20120127190847.GQ31397@adacore.com \
    --to=brobecker@adacore.com \
    --cc=asmwarrior@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=xunxun1982@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).