From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: gdb@sourceware.org
Subject: Re: Slowdown of the response from the command line?
Date: Thu, 04 Mar 2010 11:21:00 -0000 [thread overview]
Message-ID: <2bf229d31003040321w3ed171a6jf3f4369cb2596882@mail.gmail.com> (raw)
In-Reply-To: <4B8F5FC0.4010103@gmail.com>
Hi Asmwarrior,
> 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.
I'd recommend one of the 7.0.90.xxxx sources:
ftp://sourceware.org/pub/gdb/snapshots/branch/
I've been using them to try and get Python working for MinGW.
> If I can remember, the gdb.exe built from snapshot of 20100302, 20100301
> always get crashed on startup either.
What do you see when gdb crashes?
> I would prefer some gdb gurus can help. Thanks.
I'm no guru by any means, but in order to create a profiling gdb one
way is to specify CFLAGS at configuration time:
$ CFLAGS="-pg" ../configure ....
Once you have a gdb binary with profiling enabled, it should produce a
profile file (a.out if memory serves), which you can then view using
'gprof a.out'.
Cheers!
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
next prev parent reply other threads:[~2010-03-04 11:21 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 [this message]
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=2bf229d31003040321w3ed171a6jf3f4369cb2596882@mail.gmail.com \
--to=ir0nh34d@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