From: Tom Tromey <tromey@redhat.com>
To: Asm_gmail <asmwarrior@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Slowdown of the response from the command line?
Date: Thu, 04 Mar 2010 18:43:00 -0000 [thread overview]
Message-ID: <m3tyswylkp.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4B8F5FC0.4010103@gmail.com> (Asm gmail's message of "Thu, 04 Mar 2010 15:22:40 +0800")
>>>>> ">" == Asm gmail <asmwarrior@gmail.com> writes:
>> 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.
I wish I knew what was the matter, but I am not a mingw user or
developer. Maybe someone here who is can look.
Tom
prev parent reply other threads:[~2010-03-04 18:43 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
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 [this message]
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=m3tyswylkp.fsf@fleche.redhat.com \
--to=tromey@redhat.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