From: Jason Molenda <jason-swarelist@molenda.com>
To: gdb-patches@sources.redhat.com
Subject: Patch to fix incorrect ChangeLog entry
Date: Wed, 05 Sep 2001 00:11:00 -0000 [thread overview]
Message-ID: <20010905001108.A16486@shell17.ba.best.com> (raw)
Please check this in - this typeo is frustrating if you're trying
to trace the history of lookup_block_symbol. There is no such
function as block_lookup_symbol.
By the way, why isn't this patch in the sources?
http://sources.redhat.com/ml/gdb-patches/2000-q1/msg00022.html
This is Tom Tromey's patch to add a "maint profile-gdb" command
and an --enable-profile to configure switch enable it. It's
invaluable if you're trying to look into performance problems -
you enable profiling for the handful of gdb commands you care about,
then turn it off right away. It helps keep the noise level low so
you can easily spot your problem. I found the source of my prolem
(guess which func :-) a minute after I had a gdb compiled with his
patch.
I would be happy to update the patch to the current sources and
repost it. I'll probably do that even if I hear nothing from anyone
here. :-) I applied it against the Apple gdb sources and the only
tricky bit was the patch to gdbint.texinfo, which applied incorrectly
without it being obvious that it failed.
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.1587
diff -u -p -r1.1587 ChangeLog
--- ChangeLog 2001/09/05 02:54:15 1.1587
+++ ChangeLog 2001/09/05 07:03:30
@@ -6528,7 +6528,7 @@ Tue Jan 30 15:14:26 2001 Andrew Cagney
2001-01-29 Michael Chastain <chastain@redhat.com>
- * symtab.c (block_lookup_symbol): Use 'namespace' parameter in
+ * symtab.c (lookup_block_symbol): Use 'namespace' parameter in
symbol comparisons in binary search.
2001-01-27 Christopher Faylor <cgf@cygnus.com>
next reply other threads:[~2001-09-05 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 0:11 Jason Molenda [this message]
2001-09-05 14:20 ` Michael Snyder
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=20010905001108.A16486@shell17.ba.best.com \
--to=jason-swarelist@molenda.com \
--cc=gdb-patches@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