From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Crosland <mjc@attbi.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb@sources.redhat.com
Subject: Re: gcc 3.2, gdb 5.2.1, solaris2.8 sparc, slow
Date: Thu, 07 Nov 2002 13:47:00 -0000 [thread overview]
Message-ID: <20021107214759.GA15353@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0211071230330.6085-100000@newport.attbi.com>
On Thu, Nov 07, 2002 at 01:17:30PM -0800, Mark Crosland wrote:
>
> The symptoms I am experiencing are long before the program is run,
> dlopen() has not been called yet my my program.
>
> gdb program
> break main (it don't come back, at least not after 15 minutes)
>
> Below is a stack trace. I generated the stack trace by doing the following
> steps
> #0 0xff1e0708 in exit ()
> from /usr/platform/SUNW,Ultra-Enterprise/lib/libc_psr.so.1
> #1 0x00075fe0 in finish_cv_type (type=0xb75de0)
> at /homedir/markc/gdb/gdb-5.2.1/gdb/gdbtypes.c:510
> #2 0x000fda40 in read_struct_type (pp=0xffbedba0, type=0xb75de0,
> objfile=0x2d67f0) at /homedir/markc/gdb/gdb-5.2.1/gdb/stabsread.c:4211
This has nothing to do with slowness or with threads. Get a current
CVS HEAD or branch snapshot and the infinite loop will be gone;
finish_cv_type no longer exists.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-11-07 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2002-11-07 13:54 ` Elena Zannoni
[not found] <Pine.LNX.4.21.0211041333560.2454-100000@newport.attbi.com>
2002-11-06 10:59 ` Mark Crosland
2002-11-07 10:36 ` Mark Crosland
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=20021107214759.GA15353@nevyn.them.org \
--to=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mjc@attbi.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