public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: asmwarrior <asmwarrior@gmail.com>
To: Joel Brobecker <brobecker@adacore.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 14:06:00 -0000	[thread overview]
Message-ID: <4F22B05B.1010402@gmail.com> (raw)
In-Reply-To: <20120127110110.GO31397@adacore.com>

On 2012-1-27 19:01, Joel Brobecker wrote:
>> 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.
> [...]
>> 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?
> 8 days worth of commits is a very small number. So if you have git,
> you could try bisect'ing until you find the commit that's responsible.
> That might help narrow down the source of the problem.
>
Hi, Joel, I did what you suggest. Finally, I definitely found that this issue was introduced by your patch in:


Author: Joel Brobecker
Date: 2012-1-26 12:20:31
Message:
Ada: allow unqualified function names in linespecs

This is the meat, where we replace the old la_symbol_name_compare
language method with the new ada_get_symbol_name_match_p.
It fixes the problem when trying to insert a breakpoint on "+".

gdb/ChangeLog:

         * language.h (symbol_name_match_p_ftype): New typedef.
         (struct language_defn): Replace field la_symbol_name_compare
         by la_get_symbol_name_match_p.
         * ada-lang.c (ada_get_symbol_name_match_p): New function.
         (ada_language_defn): Use it.
         * linespec.c (struct symbol_matcher_data): New type.
         (iterate_name_matcher): Rewrite.
         (iterate_over_all_matching_symtabs): Pass a pointer to
         a symbol_matcher_data struct to expand_symtabs_matching
         instead of just the lookup name.
         * c-lang.c, d-lang.c, jv-lang.c, m2-lang.c, objc-lang.c,
         opencl-lang.c, p-lang.c, language.c: Delete field
         la_symbol_name_compare, and replace by NULL for new field
         la_get_symbol_name_match_p.
         * symfile.h (struct quick_symbol_functions): Update comment.
----
Modified : gdb/ChangeLog
Modified : gdb/ada-lang.c
Modified : gdb/c-lang.c
Modified : gdb/d-lang.c
Modified : gdb/f-lang.c
Modified : gdb/jv-lang.c
Modified : gdb/language.c
Modified : gdb/language.h
Modified : gdb/linespec.c
Modified : gdb/m2-lang.c
Modified : gdb/objc-lang.c
Modified : gdb/opencl-lang.c
Modified : gdb/p-lang.c
Modified : gdb/symfile.h


Can you have a look at this patch? Thanks.



asmwarrior
ollydbg from codeblocks' forum

  reply	other threads:[~2012-01-27 14:06 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 [this message]
     [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
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=4F22B05B.1010402@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=brobecker@adacore.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).