Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Asm_gmail <asmwarrior@gmail.com>
To: tromey@redhat.com
Cc: gdb@sourceware.org
Subject: Re: Slowdown of the response from the command line?
Date: Thu, 04 Mar 2010 07:24:00 -0000	[thread overview]
Message-ID: <4B8F5FC0.4010103@gmail.com> (raw)
In-Reply-To: <m3fx4noqew.fsf@fleche.redhat.com>

On 2010-2-27 1:30, Tom Tromey wrote:
> I haven't noticed it, but I think the best way to find it is to profile.
> I think you can build a -pg gdb and use maint set profile to profile a
> single command, though I have not tried this in a long time.
>
> Tom
>    

Hi, Tom, thanks for your reply.
For me, I only work under Windows till now, so I don't know how to debug 
or profile gdb under Windows.

Today, I have download the latest snapshot of gdb from:
ftp://sourceware.org/pub/gdb/snapshots/current/gdb-7.1.50.20100304.tar.bz2
And I build gdb.exe(I use TDM GCC 4.4.1 mingw32 on windowsXP) with expat 
enabled. Too bad, I even can't start debugging, when I start debugging, 
I always get the gdb.exe crashed.

If I can remember, the gdb.exe built from snapshot of 20100302, 20100301 
always get crashed on startup either.

just like Chris Sutcliffe's post in
http://sourceware.org/ml/gdb/2010-01/msg00189.html and
http://sourceware.org/ml/gdb/2010-01/msg00190.html, he has encountered 
the same problem as me in both mingw64 and mingw32.

I would prefer some gdb gurus can help. Thanks.

Asmwarrior




  reply	other threads:[~2010-03-04  7:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 16:48 asm warrior
2010-02-26 22:12 ` Tom Tromey
2010-03-04  7:24   ` Asm_gmail [this message]
2010-03-04 11:21     ` Chris Sutcliffe
2010-03-04 12:01       ` asm warrior
2010-03-04 14:12       ` asm warrior
2010-03-05  2:13         ` Chris Sutcliffe
2010-03-05  2:45       ` Asm_gmail
2010-03-04 18:43     ` Tom Tromey

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=4B8F5FC0.4010103@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.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