From: xunxun <xunxun1982@gmail.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: [mingw] gdb eat a lot of memory and slowly when start an inferior
Date: Fri, 27 Jan 2012 13:17:00 -0000 [thread overview]
Message-ID: <4F22A3EB.7050204@gmail.com> (raw)
In-Reply-To: <4F228353.3010707@gmail.com>
äº 2012/1/27 18:58, asmwarrior åé:
> I have two version of gdb build under mingw. One is build from gdb cvs
> 2012-01-19, and the other is from gdb cvs 2012-01-27.
>
> The former one works OK, when I debug Codeblocks, the start the
> inferior(Codeblocks with many plugin dlls) time is about 30 seconds,
> and gdb eat about 130M memory when the inferior start-up(I can see it
> from Windows task manager).
>
> The later one works badly, it takes more than 90 seconds to start the
> inferior, and gdb eat about 500+M memory.
>
> I guess that the total debug information of all the Codeblocks.exe and
> many dlls were loaded to memory in the second case.
>
> Any one can give a direction? I guess the commits between 2012-01-19
> and 2012-01-27 cause this issue. Mostly the handling shared library
> patches?
You can try gdb without python to check if it is related with python
modules?
>
> Thanks.
>
> asmwarrior
> ollydbg from codeblocks' forum
--
Best Regards,
xunxun
next prev parent reply other threads:[~2012-01-27 13:17 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
2012-01-28 1:33 ` asmwarrior
2012-01-27 13:17 ` xunxun [this message]
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=4F22A3EB.7050204@gmail.com \
--to=xunxun1982@gmail.com \
--cc=asmwarrior@gmail.com \
--cc=gdb@sourceware.org \
/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).