Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Crosland <mjc@attbi.com>
To: gdb@sources.redhat.com
Subject: gcc 3.2, gdb 5.2.1, solaris2.8 sparc, slow
Date: Wed, 06 Nov 2002 10:59:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0211060927430.4672-100000@newport.attbi.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0211041333560.2454-100000@newport.attbi.com>


I noticed a recent thread regarding rather slow response from gdb. I am
experiencing the same thing on solaris 2.8, sparc platform. It is an
enterpirse class server, not the fastest thing sun makes, but not slow.

I built gcc 3.2
../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld
--disable-nls --prefix=/homedir/markc/gcc --enable-languages=c,c++
--enable-shared --enable-threads

and then built gdb 5.2.1
mkdir build
cd build
/full/path/to/configure
make

using gnu make 3.77

solaris 2.8 sparc

gdb responds with the most simple programs, but anything that isn't dirt
simple seems to cause it to take forever to do basic commands.

I do "gdb myProgram", it starts right up, get the gdb prompt.

"info address main" never returns
"break main" never returns

CPU is peaked by gdb process

If I say "run", it eventualy runs

the program that is being run in gdb runs fine outside the debugger, isn't
really all that large, runs on several platforms, etc... it does load some
relatively average sized shared libraries (both from the OS and using
dlopen()). The program is multi-threaded.

It is a c++ and c program

The modules that contain main are compiled with -g. nm from binutils shows
lots of symbols.

trying to get away from Sun compiler, but a debugger is a critical
piece...

???

Mark,


       reply	other threads:[~2002-11-06 18:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0211041333560.2454-100000@newport.attbi.com>
2002-11-06 10:59 ` Mark Crosland [this message]
2002-11-07 10:36   ` Mark Crosland
2002-11-07 10:42 Garriss, Michael
2002-11-07 12:21 ` Elena Zannoni
2002-11-07 13:17   ` Mark Crosland
2002-11-07 13:47     ` Daniel Jacobowitz
2002-11-07 13:54     ` Elena Zannoni

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=Pine.LNX.4.21.0211060927430.4672-100000@newport.attbi.com \
    --to=mjc@attbi.com \
    --cc=gdb@sources.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