From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: very very slow symbol searches
Date: Thu, 23 Jan 2003 01:45:00 -0000 [thread overview]
Message-ID: <20030123014548.GA19978@nevyn.them.org> (raw)
In-Reply-To: <1043284590.7612.9.camel@Dragon>
On Wed, Jan 22, 2003 at 05:16:29PM -0800, Martin M. Hunt wrote:
> More details. The slowdown is caused by using the glibc regex. Why
> would that make it so much slower? Don't know yet. Anyway forcing GDB
> to use the included regex in libiberty fixes the problem.
>
> 2003-01-02 Mark Kettenis <kettenis@gnu.org>
>
> * configure.in: Rewrite check for GNU regex and the
> --without-included regex option, and move it into the "Checks
> for
> library functions" section. This makes us use the system regex
> again by default on systems with version 2 of the GNU C library.
> This was apparently broken.
> * gdb_regex.h [!USE_INCLUDED_REGEX] (_REGEX_RE_COMP): Define.
> * acconfig.h (USE_INCLUDED_REGEX): Remove.
> * config.in, configure: Regenerated.
Sigh, let me gues, is your host glibc version 2.3? The regex engine
was rewritten, not always for the better.
Some performance issues were fixed recently in the glibc CVS.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-23 1:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 11:58 Martin M. Hunt
2003-01-22 15:02 ` Elena Zannoni
2003-01-22 17:41 ` David Carlton
2003-01-22 19:36 ` Andrew Cagney
2003-01-22 20:46 ` Martin M. Hunt
2003-01-23 1:14 ` Martin M. Hunt
2003-01-23 1:45 ` Daniel Jacobowitz [this message]
2003-01-23 2:43 ` Martin M. Hunt
2003-01-23 6:10 ` Eli Zaretskii
2003-01-23 16:54 ` Daniel Jacobowitz
2003-01-23 20:06 ` Andrew Cagney
2003-01-22 18:26 ` David Carlton
2003-01-22 18:44 ` David Carlton
2003-01-26 7:48 ` Martin M. Hunt
2003-01-27 17:03 ` Andrew Cagney
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=20030123014548.GA19978@nevyn.them.org \
--to=drow@mvista.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